| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 208647642
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:nonincremental_builds_test
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: I06fcc0ca713cbc65c677f23dee4171b9be4d7b11
Closes #5884.
Change-Id: I06fcc0ca713cbc65c677f23dee4171b9be4d7b11
PiperOrigin-RevId: 208646495
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 208646319
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This works around the following error:
java.lang.NoSuchMethodError: java.nio.ByteBuffer.clear()Ljava/nio/ByteBuffer;
at com.google.devtools.build.lib.profiler.Profiler$BinaryFormatWriter.run(Profiler.java:949)
at java.lang.Thread.run(Thread.java:748)
JDK 9 introduced an overloaded methods with covariant return type.
Closes #5886.
PiperOrigin-RevId: 208642556
|
|
|
|
|
|
|
|
| |
removed "sychronized" from Reporter.handle() as we want to be able to let
EventHandlers care about their own synchronization.
RELNOTES: None.
PiperOrigin-RevId: 208628638
|
|
|
|
|
|
|
| |
Cleaning up all references to in-memory tools/defaults:* package.
RELNOTES:none
PiperOrigin-RevId: 208610485
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:skylark_flag_test
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: Ib698ddcfb2106fe4b9830da9b969e51271e91f58
Closes #5871.
Change-Id: I382c01d4dd8d9ee030dc8fe190a50bd7a57f8ee4
PiperOrigin-RevId: 208606660
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:incompatible_changes_conflict_test
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: I9f599b3ac8e85f394320989a71c00547b493efca
Closes #5870.
Change-Id: I7fa6db3df8d5d06ac2849d538ed6d84030cb1069
PiperOrigin-RevId: 208604220
|
|
|
|
|
|
|
| |
Note that it is currently only used by the java_proto_library family of rules (if enabled per flag).
RELNOTES: None
PiperOrigin-RevId: 208601730
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Continuous build failure
*** Original change description ***
Enable proto based resource shrinking.
RELNOTES: None
PiperOrigin-RevId: 208572831
|
|
|
|
|
|
| |
getNestedArtifact).
PiperOrigin-RevId: 208565138
|
|
|
|
|
|
|
|
| |
node having the same priority, later enqueueings having higher priority, re-enqueued nodes having highest priority, and new root nodes having lowest priority. Experimentally, this can save significant RAM (1.4G in some builds!) while not affecting speed.
Also do a semi-drive-by deleting ExecutorFactory parameter to AbstractQueueVisitor, since it was always AbstractQueueVisitor.EXECUTOR_FACTORY.
PiperOrigin-RevId: 208560889
|
|
|
|
|
|
|
|
|
| |
We use a fixed version of the previous algorithm. See the comments for details.
Fancier algorithms exist. I thought of a cool one that makes use of BatchKeyedLocker (would give me an excuse to revive it, heh), but fancy algorithms would be overkill. As noted in the initial commit of NaiveMultisetSemaphore, performance isn't critical.
RELNOTES: None
PiperOrigin-RevId: 208560559
|
|
|
|
|
|
|
| |
to ensure output contains valid stack map tables.
context: https://github.com/bazelbuild/bazel/issues/5855
PiperOrigin-RevId: 208555048
|
|
|
|
| |
PiperOrigin-RevId: 208554171
|
|
|
|
|
|
| |
This is to allow OptionsProviders to access the new skylark options which aren't held in a fragment class like native options and thus can't be accessed with the traditional <code>get</code> method. Currently this function isn't called anywhere and would just return an empty map. But in the future it will return a map of skylark flag names to values.
PiperOrigin-RevId: 208552510
|
|
|
|
| |
PiperOrigin-RevId: 208549418
|
|
|
|
|
|
|
|
|
| |
This brings 1.2x speedup to clean local Android builds.
Fixes https://github.com/bazelbuild/bazel/issues/5771
RELNOTES: For Android incremental dexing actions, Bazel now persists its DexBuilder process across individual actions. From our benchmarks, this results in a 1.2x speedup for clean local builds.
PiperOrigin-RevId: 208546936
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 208532627
|
|
|
|
|
|
|
|
|
| |
Move finding used resources to ProtoResourceUsageAnalyzer for correctness and memory improvements.
New report format: now records the kept resource along with the resource that keep it, as well maintaining the root status for each resource.
Example line: {number/foo[isRoot: false] = 0x07f...} => [{array/foos[isRoot: true] = 0x...}...]
RELNOTES: None
PiperOrigin-RevId: 208529350
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 208525880
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 208523963
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 208509424
|
|
|
|
|
|
|
| |
Move the message-digest cloning to DigestHashFunction and out of Fingerprint, to make it possible to configure Fingerprint to use different hash functions. We keep the default MD5 for now, we'd like it to use the global default but want to isolate the configuration change from any change adding potential contention.
RELNOTES: None.
PiperOrigin-RevId: 208502993
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:cpp_test
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: I7dd4ce2b5702e5853ee357ab4f2a728af7d3018d
Closes #5874.
Change-Id: I7dd4ce2b5702e5853ee357ab4f2a728af7d3018d
PiperOrigin-RevId: 208484274
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:rc_options_test
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: I1fe42e1477e9ebfb94ccfb896de4af5a72e3bb61
Closes #5873.
Change-Id: I1fe42e1477e9ebfb94ccfb896de4af5a72e3bb61
PiperOrigin-RevId: 208479907
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Using a thread-safe container to store handlers.
- Using a ThreadLocal NumberFormat to produce readable action counts.
NumberFormat (or rather the default implementation DecimalFormat) use
internal state and locking.
- Adding a lock-free fast path for START and FINISH events in
ExperimentalEventHandler.
RELNOTES: None.
PiperOrigin-RevId: 208479896
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:ui_test
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: I6667e55f26b9f87437234ba949a521760cfaaa18
Closes #5872.
Change-Id: I6667e55f26b9f87437234ba949a521760cfaaa18
PiperOrigin-RevId: 208476786
|
|
|
|
|
|
|
|
|
| |
Add a test verifying that bazel sync can be used to follow a branch
of an upstream git repository. As this is a standard use case for
bazel sync, we better verify it works properly.
Change-Id: Ia08686376e6c7a89e7f1c130129b46764e43918b
PiperOrigin-RevId: 208464247
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 208462186
|
|
|
|
|
|
|
|
|
|
| |
files and C++ headers
This change completes the handling of proto_src_root when it comes to inclusion of protos, generating the proto files in the right place and adding the generated headers to the include paths.
WANT_LGTM=elenairina
RELNOTES: None.
PiperOrigin-RevId: 208457740
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:configured_query_test
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: I51990b2b1d675dabb4d9e82bbaf6c8c0f26c4baf
Closes #5845.
Change-Id: I51990b2b1d675dabb4d9e82bbaf6c8c0f26c4baf
PiperOrigin-RevId: 208438117
|
|
|
|
|
|
| |
TransitiveVersionTable uses futures.
PiperOrigin-RevId: 208402465
|
|
|
|
|
|
|
|
| |
computeTransitivelyUsedModules to return early on missing values instead of
starting to create datastructures.
RELNOTES: None.
PiperOrigin-RevId: 208351193
|
|
|
|
|
|
|
| |
need them later.
RELNOTES: None.
PiperOrigin-RevId: 208345603
|
|
|
|
|
|
|
|
|
|
|
|
| |
when they're actually being put into a committed value. The previous behavior submitted deps' events twice, when the dep was added and when the node finished building.
The intention is to build on this refactoring to cut off events/postables across the analysis-execution boundary, so that actions are not carrying around nested sets of warnings coming from their configured targets. This will be safe because to execute an action, we must already have analyzed its configured target, so the warning would have been emitted there.
As can be seen from the changed test, this is not a pure behavior no-op. We will now emit cached events slightly later, on value committal, rather than on first dep declaration. This should not be an issue: since the events are cached, the user must have already seen them on a prior build, so the delay should not be important.
Inversely, we now report events slightly more quickly during bubbling up, since we report them at each stage, as opposed to just at ParallelEvaluator evaluation completion.
PiperOrigin-RevId: 208316502
|
|
|
|
|
|
| |
Closes #5770.
PiperOrigin-RevId: 208269268
|
|
|
|
|
|
|
| |
This CL updates the data binding to the latest public release.
RELNOTES: update data binding to 3.2.0
PiperOrigin-RevId: 208267702
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolling forward with assets being included after relinking.
*** Original change description ***
Automated rollback of commit bab4b04ad09a571615d04aacadf8b3a2b820ba5f.
*** Reason for rollback ***
Appears to cause issues with the new apk.
*** Original change description ***
Relink instead of convert proto apks.
RELNOTES: None
PiperOrigin-RevId: 208245517
|
|
|
|
|
|
|
| |
These show up as directories. Filter these out and return null from the path converter, which should cause omission of those files from any build events.
RELNOTES: None
PiperOrigin-RevId: 208244910
|
|
|
|
|
|
|
| |
This changes the logging logic slightly to support diffing startup options between different runs that have different numbers of args.
RELNOTES: Add more detailed reporting of the differences between startup options.
PiperOrigin-RevId: 208239665
|
|
|
|
|
|
|
|
|
|
|
| |
Import the current version of https://github.com/bazelbuild/remote-apis/ into Bazel to enable Remote API V2 migration.
Change-Id: I245c8514adedfa443e3ffd41a54714f40fc193c4
Closes #5605.
Change-Id: I245c8514adedfa443e3ffd41a54714f40fc193c4
PiperOrigin-RevId: 208236825
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollforward with deduplication of traversals and regression test.
RELNOTES: None
*** Original change description ***
Automated rollback of commit 39974a43abdd32e3a1acbc7da945b08da9983e4e.
*** Reason for rollback ***
b/112458627
*** Original change description ***
Allow skyframe-aware actions to pass partial results through ActionExecutionContext.
Remove FilesetProvider.
PiperOrigin-RevId: 208231719
|
|
|
|
|
|
| |
wildcarding on the presence of an includes attribute.
PiperOrigin-RevId: 208225306
|
|
|
|
|
|
|
|
|
| |
...in a single event instead of relying on the synchronisation on the
reporter. In this way, it will be possible to focus on output of errors,
and also to deduplicate warnings.
Change-Id: I9669e8497ca6e22a01f3e285ec9ee42c1ecf3fb5
PiperOrigin-RevId: 208223882
|
|
|
|
|
|
| |
TargetParsingCompleteEvent.
PiperOrigin-RevId: 208217102
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
b/112458627
*** Original change description ***
Allow skyframe-aware actions to pass partial results through ActionExecutionContext.
Remove FilesetProvider.
PiperOrigin-RevId: 208213955
|
|
|
|
|
|
|
|
|
| |
After this changes blaze will not use in-memory //tools/defaults package.
Instead of that blaze will read //tools/defaults/BUILD file from file system.
Which is empty for bazel.
RELNOTES:none
PiperOrigin-RevId: 208206605
|
|
|
|
|
|
|
|
| |
with an integration test.
Closes #5848.
PiperOrigin-RevId: 208203634
|