| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 179844898
|
|
|
|
| |
PiperOrigin-RevId: 179841278
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179838936
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 179838832
|
|
|
|
|
|
| |
Preparatory step for removing ConfigurationTransition.HOST.
PiperOrigin-RevId: 179838374
|
|
|
|
|
|
|
|
| |
This is in preparation for merging FileArtifactValue and FileStateValue.
Progress on #3360.
PiperOrigin-RevId: 179832948
|
|
|
|
|
|
| |
Only the sandbox uses the cached version. We can let it do its own caching of the top-level directory. It won't help with higher-level directories, but if there are a lot of inputs in the same directory we'll avoid I/O there.
PiperOrigin-RevId: 179830651
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous tests (internal-only, sorry) were checking for the total
number of misses before testing for the actual breakdown by reason.
This was confusing because the total number was quite mysterious and
because a test failure would point at the total instead of the
breakdown, making the test problems harder to understand.
To resolve this: check for the miss reasons first, which will give a
better indication of what's wrong with the test, and then check for the
total using a number that is derived from the breakdown, which avoids a
magical number in the test.
RELNOTES: None.
PiperOrigin-RevId: 179830122
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 179830085
|
|
|
|
|
|
|
|
| |
A native implementation of this (instead of using FileSystemUtils, which can only use public interfaces) should be more efficient and more easy to make correct.
In particular, it should allow removing FileSystemUtils#createDirectoriesAndParents, which has poor thread safety characteristics. The latter method has a lot of logic that forces certain unnatural atomicity guarantees on createDirectory, and it also has logic that is conditional on sub-string content of exception messages.
PiperOrigin-RevId: 179819623
|
|
|
|
|
|
| |
cc_toolchain_type //tools/cpp:toolchain_type.
PiperOrigin-RevId: 179818065
|
|
|
|
|
|
|
|
| |
Remove WalkableGraph#isUpToDate and BuildDriver#alreadyEvaluated and delegate the
work to implementation.
RELNOTES: None
PiperOrigin-RevId: 179815374
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 179815290
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current checks used in several places for whether an LTO indexing
step is needed only looked for direct LTO bitcode inputs. Instead we should
use the existing hasLtoBitcodeInputs() method to look both at the direct
inputs as well as inputs on all LibraryToLink. This was already used in
similar checking on the CppBinary. With this change, all places that
test for needing an LTO indexing step use the correct interface.
RELNOTES: None
PiperOrigin-RevId: 179812972
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179810894
|
|
|
|
|
|
|
|
| |
The documentation refers the `executable` attribute that doesn't exist for
`attr.label_list` or `attr.label_keyed_string_dict`. Also it doesn't explain
what the available options for `cfg` mean.
PiperOrigin-RevId: 179807288
|
|
|
|
|
|
|
| |
A new constructor is exposed for building an already-exported SkylarkProvider. The existing constructor no longer takes a name argument (since it was almost entirely ignored). The contract around the name arg for BaseFunction has been refined: it is null if the subclass provides its own naming mechanism.
RELNOTES: None
PiperOrigin-RevId: 179804491
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Fixed the single-character typo.
*** Original change description ***
Automated rollback of commit 48ff6e00e2cf72fa920d01ec78755882ab1ee313.
*** Reason for rollback ***
Breaks Copybara due to leak check failure.
*** Original change description ***
Mention that the $(JAVA) and $(JAVABASE) variables are only available if the Java runtime is listed as a toolchain.
RELNOTES: None.
PiperOrigin-RevId: 179799039
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Copybara due to leak check failure.
*** Original change description ***
Mention that the $(JAVA) and $(JAVABASE) variables are only available if the Java runtime is listed as a toolchain.
RELNOTES: None.
PiperOrigin-RevId: 179791521
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the case that a node is already done when evaluation starts, we now report
events and postables early, rather than waiting until the end of evaluation.
This makes reporting more timely, and ensures reporting even if the evaluation
is interrupted.
This caused a problem with moving the TargetCompleteEvent into Skyframe
(unknown commit). I added two unit tests at the Skyframe level to cover the
guarantees that we need for that.
Note that the replay call in constructResult can duplicate the events from
a cache hit - this is not a problem since the replaying visitor automatically
removes duplicates (and it wasn't obvious which keys correspond to cache
hits).
PiperOrigin-RevId: 179788157
|
|
|
|
|
|
|
| |
Java runtime is listed as a toolchain.
RELNOTES: None.
PiperOrigin-RevId: 179787891
|
|
|
|
| |
PiperOrigin-RevId: 179785531
|
|
|
|
|
|
| |
Closes #4282.
PiperOrigin-RevId: 179783690
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks guitar tests
*** Original change description ***
Allow --javabase to accept java_runtime (not just java_runtime_suite)
Fixes bazelbuild/bazel#3407
PiperOrigin-RevId: 179771492
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 179760609
|
|
|
|
|
|
|
| |
be consistent with LinuxSandboxUtil.
RELNOTES: None.
PiperOrigin-RevId: 179758847
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 179757650
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/e6940a554bfbd79e3e4534100fb7bf92be87cab2.
RELNOTES: None
PiperOrigin-RevId: 179756852
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This removes the main barrier to making host transitions routine
patch transitions.
Today you signify a host transition by calling
Attribute.Builder.cfg(ConfigurationTransition.HOST). Blaze's
configuration machinery auto-converts this to
HostTransition.INSTANCE, which is a patch transition.
This change provides the groundwork for removing
ConfigurationTransition.HOST and removing the special conversion
logic. This also paves the way for better API support for
multiple host configurations.
Also change some cfg(HOST) rule references to
cfg(HostTransition.INSTANCE).
PiperOrigin-RevId: 179754619
|
|
|
|
|
|
|
|
| |
This has been a no-op for a while.
RELNOTES[INC]: android_* rules no longer support legacy_native_support attribute.
PiperOrigin-RevId: 179749745
|
|
|
|
| |
PiperOrigin-RevId: 179748374
|
|
|
|
|
|
|
| |
rt.jar etc. no longer exist, retrieve the default bootclasspath contents
using a Java program instead.
PiperOrigin-RevId: 179747945
|
|
|
|
|
|
|
| |
late bound default instead.
RELNOTES: None.
PiperOrigin-RevId: 179738235
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179737025
|
|
|
|
| |
PiperOrigin-RevId: 179735701
|
|
|
|
|
|
| |
Fixes bazelbuild/bazel#3407
PiperOrigin-RevId: 179735489
|
|
|
|
|
|
| |
Closes #4326.
PiperOrigin-RevId: 179734266
|
|
|
|
|
|
| |
it inside ConfiguredTargetKey instead of having a BuildConfiguration there, so it's going to be more widely used.
PiperOrigin-RevId: 179734211
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 179733057
|
|
|
|
|
|
|
|
| |
Fix a bug where Bazel would crash if two Directory protos had the same
hash.
RELNOTES: Remote Caching and Execution support output directories.
PiperOrigin-RevId: 179731040
|
|
|
|
|
|
| |
same information and is more useful, since it's practically a SkyKey.
PiperOrigin-RevId: 179727105
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 179723648
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 179722149
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 179719177
|
|
|
|
|
|
|
| |
that use the linux-sandbox tool, irrespective of which SpawnRunner they use.
RELNOTES: None.
PiperOrigin-RevId: 179716067
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 179707811
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179705357
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
--auth_* flags only work with Google Cloud Authentication. That's
confusing and restricts the naming of more general purpose authentication
flags that we might want to add in the future. So instead of --auth_*
let's call them --google_* (the old ones will continue working for a
while).
Also, --auth_enabled (aka --google_default_credentials) is no longer required
when specifying --auth_credentials (aka --google_credentials).
So now there's two simple ways to authenticate with Google Cloud:
* bazel build --google_default_credentials
* bazel build --google_credentials=creds.json
RELNOTES: --auth_* flags were renamed to --google_* flags. The old names
will continue to work for this release but will be removed in the next
release.
Change-Id: Ia1736f32e15a37995be3172cd9608d518ddeab44
PiperOrigin-RevId: 179700832
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179697088
|
|
|
|
|
|
|
| |
merge actions.
RELNOTES: none
PiperOrigin-RevId: 179695515
|