| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
| |
--
Change-Id: I699d605b3dc923a60516d70dc5d0144a9be49b0b
Reviewed-on: https://bazel-review.googlesource.com/#/c/6310/1
MOS_MIGRATED_REVID=134466041
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134464786
|
|
|
|
|
|
|
| |
in android_* targets (behind existing flag).
--
MOS_MIGRATED_REVID=134453743
|
|
|
|
|
|
|
| |
false.
--
MOS_MIGRATED_REVID=134452391
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke installation on latest release.
Fixes #1846
*** Original change description ***
Reintroduce .bazelrc and set --action_env defaults
Shipping a .bazelrc was removed in 009b48bcfaf4ebb17f9ab03bea9036cfa3c12ff0.
However, as per our "Specifying environment variables for actions" design
document, we want to ship a global rc file specifying the common environment
variables to be inherited. So revert that change and add the desired entries
to the global bazelrc file we're shipping.
--
MOS_MIGRATED_REVID=134450299
|
|
|
|
|
|
|
|
|
| |
This entails adding a read-locking mechanism to Mutability contexts.
RELNOTES[INC]: Updating list/dicts while they are being looped over is not allowed. Use an explicit copy if needed ("for x in list(mylist):").
--
MOS_MIGRATED_REVID=134442701
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Current change do not include version number. Include the version
number in the artifact.
Closes #1841.
--
Change-Id: I2516527829ec28c7c9abea2424f2e7d9585af9b0
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1841
MOS_MIGRATED_REVID=134422109
|
|
|
|
|
|
|
|
|
|
| |
Of course, the sources of the buildevent protos should be visible by
the including srcs targets.
--
Change-Id: I76f5155990dd767d5eb46ad7150980589050217e
Reviewed-on: https://bazel-review.googlesource.com/#/c/6290
MOS_MIGRATED_REVID=134414797
|
|
|
|
|
|
|
|
|
|
| |
EvaluationProgressReceiver objects have two common naming schemes
currently, and calling them invalidationReceiver is misleading, so to
make the naming convention standard, all object names are based on
"progressReceiver."
--
MOS_MIGRATED_REVID=134411011
|
|
|
|
|
|
|
| |
protos from linking into the final binary.
--
MOS_MIGRATED_REVID=134409481
|
|
|
|
|
|
|
|
|
| |
PackageCacheOptions as a bundle.
This will allow me to thread a new flag through more easily in the future.
--
MOS_MIGRATED_REVID=134406676
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add the basic protocol buffers needed for an event stream. This will
eventually become a public interface, but is not complete yet. In
particular, users should expect it to be extended over time and handle
the following kind of changes should gracefully.
- New fields can be added to any protocol buffer, and
- new choices of event protocol buffers can be added to the payload.
--
Change-Id: Ie4d1fdaa4f1aec6c5002ad94da4ef14112f8303f
Reviewed-on: https://bazel-review.googlesource.com/#/c/6271
MOS_MIGRATED_REVID=134405277
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134403060
|
|
|
|
|
|
|
| |
As suggested by klimek in the review (I had already submitted at that point). I confirmed that this test fails if I undo commit 78b9cab45de2a32158cd4306cd40208045cf6f85.
--
MOS_MIGRATED_REVID=134400910
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When `compile.sh` builds bazel using bazel, it
copies the resulting binary to `output/bazel`.
However sometimes the convenience symlink
`bazel-bin` is not created, probably because an
old one is still around and cannot be deleted.
That is clearly a bug, but to work around it, the
bootstrap builder shouldn't attempt to rely on the
creation of these symlinks in the first place.
This change updates compile.sh to use `bazel info`
to locate the `bazel-bin` directory's real path,
and attempt to copy the bazel binary from there.
This works around
https://github.com/bazelbuild/bazel/issues/1827
--
MOS_MIGRATED_REVID=134398451
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134378592
|
|
|
|
|
|
|
|
|
| |
Those dependencies are not needed at runtime.
Fixes #1834.
--
MOS_MIGRATED_REVID=134373693
|
|
|
|
|
|
|
| |
which allows propagation of keys to only the direct dependers of a provider.
--
MOS_MIGRATED_REVID=134337199
|
|
|
|
| |
MOS_MIGRATED_REVID=134334656
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134321948
|
|
|
|
|
|
|
| |
This should now get appropriately embedded into @bazel_tools.
--
MOS_MIGRATED_REVID=134319465
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134312343
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Break Bazel bootstrap on JDK7
*** Original change description ***
Skylark: Give more detailed errors when parsing the arguments
of a SkylarkCallable.
--
MOS_MIGRATED_REVID=134309621
|
|
|
|
|
|
|
|
|
| |
Pass "-c opt" when building bazel.
Fixes https://github.com/bazelbuild/bazel/issues/1830
--
MOS_MIGRATED_REVID=134307054
|
|
|
|
|
|
|
| |
The planned replacement of the ApkBuilder with singlejar uses it.
--
MOS_MIGRATED_REVID=134290339
|
|
|
|
|
|
|
| |
sandbox directories could not be cleaned up.
--
MOS_MIGRATED_REVID=134286101
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1742
MOS_MIGRATED_REVID=134283632
|
|
|
|
|
|
|
| |
...instead of pulling in symbols from indirect dependencies.
--
MOS_MIGRATED_REVID=134283492
|
|
|
|
|
|
|
| |
occasional hangs seen during builds and on Bazel CI.
--
MOS_MIGRATED_REVID=134279208
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The bootstrap build is special in that it does not
use the Bazel client hence we cannot pass a
--bazelrc flag as there'd be nothing to parse it.
While Bazel is being bootstrapped it's nice to
have colors on a smart terminal, but when the
bootstrapping is done by Jenkins as part of a CI
test, we need the output to be readable, i.e. be
free of control characters, so we should pass
--colors=no for example.
By exporting BAZEL_BOOTSTRAP_STARTUP_OPTIONS the
user can control what startup flags will the
bootstrap build use, so we can pass these
dumbing-down flags during CI builds.
--
MOS_MIGRATED_REVID=134273969
|
|
|
|
|
|
|
| |
SandboxExecRoot#copyOutputs could hide an earlier ExecException from SandboxRunner#run in the Darwin and Linux sandbox strategies.
--
MOS_MIGRATED_REVID=134273806
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/1786
--
MOS_MIGRATED_REVID=134271340
|
|
|
|
|
|
|
| |
of a SkylarkCallable.
--
MOS_MIGRATED_REVID=134266707
|
|
|
|
|
|
|
|
|
| |
These changes could help use build TensorFlow on Windows
--
Change-Id: I98962add450da234d5965b091607817e991af383
Reviewed-on: https://bazel-review.googlesource.com/#/c/6270
MOS_MIGRATED_REVID=134266671
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/1826
--
MOS_MIGRATED_REVID=134261731
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134221884
|
|
|
|
|
|
|
|
|
|
|
| |
--experimental_dynamic_configs=notrim mode (since
the whole point of calling it is to figure out which fragments to trim).
This shaves a 25% analysis time penalty over static configs down to 19%.
--
MOS_MIGRATED_REVID=134130771
|
|
|
|
|
|
|
|
|
| |
places we wait for tasks (plural!) submitted to a ForkJoinPool to finish since we actually want to do so interruptibly.
As was to be expected, testing this was tricky :)
--
MOS_MIGRATED_REVID=134128019
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134120579
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134118816
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134116487
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134110312
|
|
|
|
|
|
|
| |
META-INF/). Unix 'file' utility uses it to distinguish jar file from zip file.
--
MOS_MIGRATED_REVID=134102453
|
|
|
|
|
|
|
| |
md5 repeatedly from bash is too slow.
--
MOS_MIGRATED_REVID=134087524
|
|
|
|
|
|
|
| |
Prevents overly large responses from overwhelming grpc.
--
MOS_MIGRATED_REVID=134083479
|
|
|
|
|
|
|
|
|
|
| |
Switch back to using the directory name, since there's no good way to get the
workspace name from `clean` (yet).
Fixes #1795.
--
MOS_MIGRATED_REVID=134083065
|
|
|
|
|
|
|
| |
RELNOTES: When using android_binary.manifest_merger="android" the merger produces a summary log next to the merged manifest artifact.
--
MOS_MIGRATED_REVID=134082985
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The link action feature configuration command line options aren't needed
in the LTO Backend compile command line. This additionally causes a failure
when trying to compile ThinLTO and FDO, as the build variables for
the FDO link options in the feature configuration are not set.
Confirmed that this is a no-op for non-FDO builds (there are no c++-link* features),
which is probably why I didn't notice this and remove it earlier. We add the
lto-backend features later in LTOBackendArtifacts.scheduleLTOBackendAction()
--
MOS_MIGRATED_REVID=134076174
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
We *still* have case discrepancies in objc code, which appears to be a hard blocker to .d pruning. This change will not work until we've found some way to enforce case-consistency.
*** Original change description ***
Implement input pruning using .d files in objc.
--
MOS_MIGRATED_REVID=134069949
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134062471
|