| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133395817
|
|
|
|
|
|
|
|
|
|
|
|
| |
by class.
TransitiveInfoProviderMap enforces that the provider implements the interface it's keyed by
and provides accessors the reduce the amount of casting. This in general reduces boilerplate throughout wherever TransitiveInfoProviders are mapped by their class.
Also add shorthand for adding a provider where it only implements TransitiveInfoProvider once, reducing the redundant specification of the TransitiveInfoProvider class. Infer the class as the exclusive direct implementor of TransitiveInfoProvider to account for special cases like AutoValue and LicenseProvider.
--
MOS_MIGRATED_REVID=133386336
|
|
|
|
|
|
|
| |
ide_info_generation.
--
MOS_MIGRATED_REVID=133374355
|
|
|
|
|
|
|
|
|
|
|
| |
On Linux, the tool is called `md5sum`, on Darwin it's
just `md5`, and their output is slightly different too.
This commit implements a wrapper that selects the right
tool for the platform.
--
MOS_MIGRATED_REVID=133370990
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133359465
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133358757
|
|
|
|
|
|
|
|
|
| |
RELNOTES: Global varaiables HOST_CFG and DATA_CFG are deprecated in favor of strings "host"
and "data.
Argument `cfg = "host"` or `cfg = "data"` is mandatory if `executable = True` is provided for a label.
--
MOS_MIGRATED_REVID=133285197
|
|
|
|
|
|
|
|
|
| |
Fixes #1739
RELNOTES: Add support for aspects to attr.label() attributes
--
MOS_MIGRATED_REVID=133275712
|
|
|
|
|
|
|
| |
function calls.
--
MOS_MIGRATED_REVID=133259901
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133257532
|
|
|
|
|
|
|
|
|
|
| |
Now that we have gotten a StartupOptions class for each of the products
we support, we can bake in the product name in each instance instead of
passing it to the constructor. Helps with encapsulation and simplifies
various instantiations of these classes.
--
MOS_MIGRATED_REVID=133255854
|
|
|
|
|
|
|
| |
merge-to-os-blaze.
--
MOS_MIGRATED_REVID=133253934
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Neither `realpath` nor `readlink -e` are available
on Mac OS X, so I implemented one using basic Bash
utilities: `readlink`, `basename`, and `dirname`.
I also implemented a `normalize_path` method that
can normalize relative or absolute path strings
(remove and resolve "." and ".." references). It
uses simple string processing and doesn't touch
the file system.
This will help fixing
https://github.com/bazelbuild/bazel/issues/1776 and
also opensourcing some shell tests that rely on
`realpath`.
--
MOS_MIGRATED_REVID=133249912
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133249815
|
|
|
|
|
|
|
| |
This test shouldn't have been submitted. It can not be properly tested in bazel because there is no specific JDK that we can use. The test is currently passing because $BLAZE_JAVABASE is an empty string and therefore bazel uses the default JDK.
--
MOS_MIGRATED_REVID=133236838
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133224703
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL is a verbatim reproduction of the following CLs, modulo adjustments
to cope with changes at HEAD:
* commit 4a45d92130a6b1306a3840d006df165b8040a6cf: Use inheritance to support site-specific options.
* commit dfb2c73eda3d2dd8787ea9b2d0a03b49dfa2acc5: Inject the product name via the per-product main.cc files.
* unknown commit: Remove the internal/external startup_options duality.
The cause that triggered the rollbacks was fixed separately in commit 69a8d7205287bedf3a6140ec9327e2fad1758c22
as prepartory work for this roll-forward, so things should work now.
--
MOS_MIGRATED_REVID=133139218
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a test script uses bash extensions, it should not call /bin/sh
which is the POSIX shell (and no further assumptions should be made).
In the long run, we should rewrite that test for the POSIX shell, but
to quickly get rid of CI breakages, it is faster to acknowledge the
bash dependency.
--
Change-Id: I179a0d17ef663d473524d80de7dc660778c23acd
Reviewed-on: https://bazel-review.googlesource.com/#/c/6071
MOS_MIGRATED_REVID=133137841
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133133457
|
|
|
|
|
|
|
|
|
|
| |
...to determine if actions have been executed; instead, as the UI to
list the subcommands and explicitly look for the action in question.
--
Change-Id: Ic46244c8daec83a7f6b27e09c366df435f36ba96
Reviewed-on: https://bazel-review.googlesource.com/#/c/6070
MOS_MIGRATED_REVID=133130712
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133119463
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133113800
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133113385
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133112586
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133101319
|
|
|
|
|
|
|
| |
Fixes #1697.
--
MOS_MIGRATED_REVID=133056813
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The result value of GetOutputRoot does not depend on the startup
options: it only depends on the environment and/or the hardcoded values
for Bazel and Blaze. Therefore, put it in the WorkspaceLayout module
just as we did for all other similar functions.
The fact that GetOutputRoot was part of BlazeStartupOptions was the root
cause behind the rollback of commit 4a45d92130a6b1306a3840d006df165b8040a6cf: in particular, that CL
silently added a virtual call to the GetOutputRoot method from the
constructor of the superclass, and this invokes undefined behavior
because the class has not yet been fully constructed. This caused Blaze
to have incorrect values for the output_root. By moving the function
out, we'll be able to roll that CL forward as it originally was.
As part of this change, add unit tests for the value of output_root
under various scenarios. These would have caught the discrepancy
introduced by that CL.
--
MOS_MIGRATED_REVID=133056251
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133045120
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...to determine which actions have to be recomputed based on changes
to the client environment. Note that this change does it the simple way
and reconsideres all actions on a changed client environment, while still
only reexecuting those, where the part that was inherited from the environment
actually did change.
--
Change-Id: Ie1116d094642165e5e959447a6fcf49d19b37d6e
Reviewed-on: https://bazel-review.googlesource.com/#/c/5431
MOS_MIGRATED_REVID=133010705
|
|
|
|
|
|
|
| |
Fixed #1765
--
MOS_MIGRATED_REVID=133006031
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks all projects using Bazel, see https://ci.bazel.io
*** Original change description ***
Deprecated and removed HOST_CFG and DATA_CFG global variables.
--
MOS_MIGRATED_REVID=133005398
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132999234
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132990129
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132985974
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132984079
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132980407
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132980076
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132976702
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132973437
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132965047
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
others in opt compiles.
A while back, we added a HIDDEN_TOP_LEVEL output group to CcBinary targets to
ensure that --process_headers_in_dependencies works as expected for them.
However, adding all HIDDEN_TOP_LEVEL files is actually too much and e.g. also
contains .pic.o files which are expensive to build but not actually needed for
the compile. The fundamental difference between CcLibrary and CcBinary targets
here is that a CcBinary already declares most of its inputs as it needs all of
them to link the binary. In contrast, CcLibraries wouldn't need any of they
dependent .o files and thus wouldn't even try to build them.
This changes splits out the header token files which are required to make
--process_headers_in_dependencies work correctly and only adds those to
HIDDEN_TOP_LEVEL outputs of binaries files.
Also removing some unused code that was producing warnings.
--
MOS_MIGRATED_REVID=132883722
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In some cases, Bazel has already been doing this.
In other cases, Bazel tried to infer the default cpu from the CROSSTOOL, but it
did not do so consistently across different configuration fragments. I.e.,
Bazel ended up with an inconsistent set of toolchains for e.g., Python, C++,
and Java.
After this change, Bazel ignores any default_cpu setting in the CROSSTOOL.
Note that the Jvm is still inconsistent with all others, as it uses "default"
as the cpu value and ignores both command-line-specified and CROSSTOOL-specified
values.
--
MOS_MIGRATED_REVID=132879102
|
|
|
|
|
|
|
|
|
| |
Also increase timeout to reduce flakyness.
--
Change-Id: Ieb5bbd9b2f9e28cd3ec39f42deb0aba0f501171c
Reviewed-on: https://bazel-review.googlesource.com/c/6033/
MOS_MIGRATED_REVID=132873805
|
|
|
|
|
|
|
|
|
| |
This also entirely disallows select() in repository rules. All repository rules should now error out if the wrong type is given, instead of printing a stack trace.
Fixes #1307.
--
MOS_MIGRATED_REVID=132872804
|
|
|
|
|
|
|
| |
--
Change-Id: I1203f15e8e02373b062142c0631ff94f14bd437d
Reviewed-on: https://bazel-review.googlesource.com/c/6032/
MOS_MIGRATED_REVID=132870643
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132870287
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132864919
|
|
|
|
|
|
|
| |
Fixes #1755.
--
MOS_MIGRATED_REVID=132861187
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132852747
|
|
|
|
|
|
|
| |
mentioned in the dynamic_runtime_libs attribute.
--
MOS_MIGRATED_REVID=132676097
|