| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
the bug that the RemoteWorker would fail to upload outputs that were too big to send in a single gRPC message.
Fixes #2822.
RELNOTES: n/a
PiperOrigin-RevId: 153710733
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, we correctly replaced CppConfiguration with HipCppConfiguration for hip
builds, but we didn't update FeatureConfiguration. As Blaze was not using
action_configs for compile actions, compiler tool was taken from configuration
at the action creation time, not from FeatureConfiguration, so the tool was
correct. Command line flags (some of them) were computed by
FeatureConfiguration, but luckily the toolchains were so similar that it
worked.
In https://github.com/bazelbuild/bazel/commit/e1d692e486a2f838c3c894fd9de693fabd6685ed I tried to use action_configs for compile actions. The result
was that compiler tool was taken from configuration at the CppConfiguration
creation time, that was put into FeatureConfiguration, and that was used in
action creation time. Sadly, the tool in CppConfiguration was different that
the tool in HipCppConfiguration, and b/37315875 was discovered.
This cl also uppdates FeatureConfiguration when HipCppConfiguration is
replaced.
RELNOTES: None.
PiperOrigin-RevId: 153710405
|
|
|
|
|
|
|
| |
Part of #2841.
Change-Id: I4d1e63aac6b5ed6beb9854b9b67d2899d8da4418
PiperOrigin-RevId: 153705466
|
|
|
|
|
|
| |
This is the first part of a two-step migration to the new versions.
Change-Id: I3835b3db386f43cd00ca0d68c7fd2a42c3f9714f
|
|
|
|
|
|
|
|
|
|
| |
This module rely on an un-maintained codepath and is hardly used by anyone.
We should also archive the code from dash until we can revive it with BEP
RELNOTES[INC]: --use_dash, --dash_url and --dash_secret are removed.
PiperOrigin-RevId: 153701824
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to lookup repositories as part of converting exec paths to artifacts,
which in turn is needed for action cache lookups. These lookups should not
cause a Skyframe exit, so we must not throw an exception here, unless the
error makes it impossible to continue. Instead, we need to leave the decision
whether to error out or not to the caller.
Note that we may unnecessarily fetch a remote repository in order to do the
action cache lookup, even if the action no longer depends on the input file,
although this should only be possible for C++ compile actions. It's possible
that there's another bug in the C++ compile action key computation that also
contributes.
This change also makes it so that the post-resolution action cache code
ignores any errors wrt. repository lookup rather than throwing. If any of the
paths could not be found, then the action cache lookup fails and we re-execute
the corresponding action, which is exactly what should happen.
Fixes #2759.
PiperOrigin-RevId: 153696243
|
|
|
|
|
|
|
| |
Fixes #2848.
RELNOTES: None.
PiperOrigin-RevId: 153692641
|
|
|
|
|
|
|
| |
list of built-in include directories available to Skylark through it.
RELNOTES: None.
PiperOrigin-RevId: 153684976
|
|
|
|
|
|
| |
Fixes #1413.
PiperOrigin-RevId: 153684106
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
The depot has been fixed: unknown commit
*** Original change description ***
Partial rollback of unknown commit
PiperOrigin-RevId: 153646328
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Causes issues with library R generation.
*** Original change description ***
Refactor the RClassGenerator to be reusable for different packages.
RELNOTES: None
PiperOrigin-RevId: 153641485
|
|
|
|
|
|
|
|
| |
The jar will be added in
https://bazel-review.googlesource.com/c/10050/
Change-Id: I6e8228f8dbc627cd22bab45ae8eda5b4f332cbda
PiperOrigin-RevId: 153634892
|
|
|
|
|
|
| |
RELNOTES: fix idempotency issue with desugaring lambdas in interface initializers for android
PiperOrigin-RevId: 153634357
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 153619067
|
|
|
|
|
|
|
|
| |
Add a dynamic equivalent for LIPO_COLLECTOR transition.
Rename LipoDataTransition (which handles DATA transition) to DisableLipoTransition. A future change will add a corresponding EnableLipoTransition (which will model TARGET_CONFIG_FOR_LIPO).
PiperOrigin-RevId: 153611898
|
|
|
|
| |
PiperOrigin-RevId: 153610163
|
|
|
|
|
|
|
| |
Added toMap()/fromMap() to OptionsParser, and moved the implementation of OptionsBase#asMap away from OptionsParserImpl.
RELNOTES: None
PiperOrigin-RevId: 153602479
|
|
|
|
|
|
| |
TESTED: local server
RELNOTES: n/a
PiperOrigin-RevId: 153599636
|
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES: Adds a --override_repository option that takes a repository
name and path. This forces Bazel to use the directory at that path
for the repository. Example usage:
`--override_repository=foo=/home/user/gitroot/foo`.
Fixes #1266
PiperOrigin-RevId: 153599291
|
|
|
|
| |
PiperOrigin-RevId: 153589856
|
|
|
|
|
| |
WANT_LGTM=all
PiperOrigin-RevId: 153584480
|
|
|
|
| |
PiperOrigin-RevId: 153584278
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is to minimize the likelihood of obscure policy conflict. Now, the last policy on
a flag (after policy expansion) will be the only one in the "canonical" invocation
policy. There should be no reason for explicitly setting multiple policies on a single
flag, but if an expansion flag is policy'd and one of its children has a more specific
policy on it, make sure that the policy on the child flag is after the policy on the
expansion flag.
Note that this restriction (only the last policy gets applied) also applies for repeatable flags. Make sure all values being set to a repeatable flag are set in a single SetValue operation, with multiple flagValues set.
PiperOrigin-RevId: 153584034
|
|
|
|
|
|
|
|
|
| |
Without this change, //src/test/shell/bazel:bazel_toolchain_test is failing
when remote caching is enabled.
Workaround for #2845.
PiperOrigin-RevId: 153574893
|
|
|
|
|
|
|
|
| |
eventually be able to fix Android builds.
Progress on #2848.
Change-Id: I3b96425c2f5a4708629882e730d4907abd1226a6
|
|
|
|
|
|
|
|
| |
..until issue #2848 is fixed. In this way, they do not shadow
new breakages on CI.
Change-Id: I95ff1aafc1431cadf387119018dfd2443185e7db
PiperOrigin-RevId: 153574737
|
|
|
|
|
|
|
|
| |
This is the Blaze side of the support for emitting and using minimized bitcode files during the LTO indexing (thin link) step of a ThinLTO build. The llvm support has already been released to stable, and this needs to be submitted after the companion Crosstool support (unknown commit, will send for review once this larger part is reviewed).
This enables large applications successfully build using ThinLTO and -g, otherwise the bitcode files that are input to the LTO indexing step are huge and the maximum input size is exceeded.
PiperOrigin-RevId: 153549687
|
|
|
|
| |
PiperOrigin-RevId: 153545346
|
|
|
|
| |
PiperOrigin-RevId: 153531483
|
|
|
|
|
|
|
|
| |
If minimum_os is unspecified on an apple_binary target and ios_multi_cpus is not set, no
apple_binary configuration transition is made.
RELNOTES: None.
PiperOrigin-RevId: 153529598
|
|
|
|
|
|
|
| |
of xctest apps are seen by ios_test
RELNOTES: None.
PiperOrigin-RevId: 153529262
|
|
|
|
|
|
|
|
| |
restrictions.
Prevent the old category strings "undocumented," "hidden," or "internal" from being used as categories, to prevent developers from relying on deprecated behavior.
PiperOrigin-RevId: 153525499
|
|
|
|
|
|
| |
docker_build.
PiperOrigin-RevId: 153508081
|
|
|
|
|
|
|
|
|
|
| |
The key change is to eliminate the need to transition from the data to the target configuration by relying on out-of-band configuration state. Specifically, the old model drops LIPO options from the data configuration. In the cases when we have to switch back (i.e. TARGET_CONFIG_FOR_LIPO), those options have to get re-injected somehow. Static configurations achieve this with the global configuration transitions table. But dynamic configs have no comparable source (and they consciously eschew global state).
This cl changes the model to *keep* LIPO settings in the data config, then use a new "enableOrDisable" flag to determine whether or not to actually use them. With this model, the data -> target transition is now as simple as toggling that flag.
This change doesn't actually add dynamic config LIPO support. It's doing enough as it is, and we need to make sure it doesn't break existing LIPO semantics. Dynamic support will come as a followup.
PiperOrigin-RevId: 153504240
|
|
|
|
|
|
| |
#2147
PiperOrigin-RevId: 153494286
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/2743.
RELNOTES: android_library exports_manifest now defaults to True.
PiperOrigin-RevId: 153493900
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 153489730
|
|
|
|
|
|
|
|
|
|
| |
This is already fixed in the CachedLocalSpawnRunner, with tests there, which
will replace RemoteSpawnStrategy in the near future. For now, I'd like to get
this in in time for 0.5.0 to get test caching working.
Fixes #1413.
PiperOrigin-RevId: 153486592
|
|
|
|
| |
PiperOrigin-RevId: 153485708
|
|
|
|
| |
PiperOrigin-RevId: 153474001
|
|
|
|
| |
PiperOrigin-RevId: 153473961
|
|
|
|
|
|
|
| |
This type is no longer used and has removed from bazel.
RELNOTES: None
PiperOrigin-RevId: 153471066
|
|
|
|
|
|
| |
All genjar actions have very short command lines.
PiperOrigin-RevId: 153468708
|
|
|
|
|
|
|
| |
They were added in https://github.com/bazelbuild/bazel/commit/3a5d3db6436bbaf5351da9ea9c19a41ae7c95ca9 by Yours Truly.
RELNOTES: None.
PiperOrigin-RevId: 153468590
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 1cd2096284959ead26687d1d58b695d2abffb8e2.
That commit tried to find a more suitable python binary by
following symlinks. That, however, is not necessary, as
our follow-up infrastructure can call symbolic links and
our tests os.path.isfile(path) and os.access(path, os.X_OK)
follow symbolic links as well.
Fixes #2836.
Change-Id: If37589622d141265577eb3872f68342ae1c263dc
PiperOrigin-RevId: 153461118
|
|
|
|
|
|
|
|
|
| |
It has been disabled in https://github.com/bazelbuild/bazel/commit/bce889840f91f14c05418d960984bcf1a5f59411 and in https://github.com/bazelbuild/bazel/commit/21fb8cac60c36cb527d6131ab0092bcdf138d99a and then was not re-enabled.
Also update src/java_tools/junitrunner/java/com/google/testing/coverage/BUILD to which I accidentally submitted a change directly to our OSS repository.
RELNOTES: None.
PiperOrigin-RevId: 153460778
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke //src/test/shell/bazel:cc_inc_library_test on darwin
see http://ci.bazel.io/job/bazel-tests/BAZEL_VERSION=HEAD,PLATFORM_NAME=darwin-x86_64/704/console
*** Original change description ***
Basic open-source crosstool to support targetting apple platform types.
RELNOTES: None.
PiperOrigin-RevId: 153460334
|
|
|
|
|
|
|
|
|
|
| |
Only write a cache entry when the spawn executed successfully, and with a 0
exit code. In the test, we only check that uploadFileContents is called exactly
twice.
Progress on #1413.
PiperOrigin-RevId: 153458240
|
|
|
|
|
|
|
|
|
| |
Reduce spaghetti code by exposing the parser's OptionsData as package-private, rather than exposing individual methods ad hoc between OptionsParser and OptionsParserImpl.
Also change some calls from static constructors to diamond syntax.
RELNOTES: None
PiperOrigin-RevId: 153457442
|
|
|
|
| |
Change-Id: I468ab58151a6e62fa9d5d640142c38cd8886737b
|