| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 169972686
|
|
|
|
| |
PiperOrigin-RevId: 169969136
|
|
|
|
|
|
| |
and error-checking for their existence is already done by the client.
PiperOrigin-RevId: 169966701
|
|
|
|
|
|
|
|
| |
Include the coverage data file into the list of files repeorted in the
test_result event in the BEP.
Change-Id: Ia7b653addd5589268ce919b3e0349371dbc18bf2
PiperOrigin-RevId: 169956864
|
|
|
|
| |
PiperOrigin-RevId: 169955807
|
|
|
|
|
|
|
|
|
|
|
|
| |
precomputed value. Instead, manually check if the value has changed, and if it has, invalidate its consuming WorkspaceStatusValue node, forcing its re-evaluation, where it will pick up the new value.
This seems more awkward than the original code, but it is more correct in spirit: injecting a precomputed value which can change even while the source state does not is a smell. Long-term, the key for the WorkspaceStatusValue should incorporate a hash of the action, and that hash should be in the configuration, just as other configuration flags are. That isn't possible right now just because we don't have configuration trimming, and we drop all nodes on configuration changes, so putting workspace status options into the configuration would lose change pruning whenever we changed workspace status options.
If/when those problems are fixed, we can extend this change to have WorkspaceStatusFunction continue to request the action out-of-band, but keyed by the hash. Then we can stop invalidating stale nodes.
See also https://github.com/bazelbuild/bazel/issues/3785.
PiperOrigin-RevId: 169947071
|
|
|
|
| |
PiperOrigin-RevId: 169942209
|
|
|
|
| |
PiperOrigin-RevId: 169938521
|
|
|
|
|
|
|
|
|
|
|
| |
Also, bundle snapshots.img in Bazel since it was removed from the SDK.
Part of the fix for https://github.com/bazelbuild/bazel/issues/3504
Note that this will require an update to unified launcher at https://github.com/google/android-testing-support-library
RELNOTES: None
PiperOrigin-RevId: 169937694
|
|
|
|
| |
PiperOrigin-RevId: 169930643
|
|
|
|
| |
PiperOrigin-RevId: 169916427
|
|
|
|
|
| |
Change-Id: I64202a318bb352c2b473f3570243f545ab9fbdc1
PiperOrigin-RevId: 169913876
|
|
|
|
|
|
|
|
|
|
| |
Set no_windows on all tests that have quoted jvm_flags. Remove no_windows from
some platform-independent unit tests.
Fixes https://github.com/bazelbuild/bazel/issues/3794
RELNOTES: None
PiperOrigin-RevId: 169909924
|
|
|
|
|
|
|
|
|
| |
errors even if not all values are present.
Fixes #3751.
Change-Id: I92fd7527384800beca80b9daac58f3a7760268b2
PiperOrigin-RevId: 169907526
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
such as from /etc/bazel.bazelrc.
Fixes https://github.com/bazelbuild/bazel/issues/3727.
This should not be the final fix. There are remaining issues:
- This test should pass regardless of the UI used (either fix the experimental UI or fix the test to make fewer assertions).
- Outside bazelrcs should not pollute the test.
But this fixes the breakage.
RELNOTES: N/A
PiperOrigin-RevId: 169906770
|
|
|
|
|
|
|
| |
Very large server instances can take >10 seconds for GC, and if they are hit at an inopportune moment, they may get killed needlessly.
RELNOTES: None.
PiperOrigin-RevId: 169905185
|
|
|
|
|
|
|
| |
Some of the arguments are not used or are always passed blank.
RELNOTES: None.
PiperOrigin-RevId: 169899161
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Relanding
https://github.com/bazelbuild/bazel/commit/17214ac78ffaec369d5d5bafe62a39730473cfaa
with fixes to 'repository_ctx.download()' and
'repository_ctx.download_and_extract()'.
I reviewed other usages of @ParamType annotation - I do not think there
are more issues.
Fixes #3714.
Change-Id: I17087ef3fc2d28ab99224740a2164675a49847d3
PiperOrigin-RevId: 169896223
|
|
|
|
|
|
|
| |
All callers passed true, so there's no need to have the boolean there.
RELNOTES: None.
PiperOrigin-RevId: 169888322
|
|
|
|
|
|
|
|
| |
In https://github.com/bazelbuild/bazel/commit/b7a9ecd08c958e9513ea234b470a0f86e89e1acd I introduced a bug when linkstamping outputs would no longer be
stored in $TEST_TMPDIR. This cl fixes that.
RELNOTES: None.
PiperOrigin-RevId: 169882831
|
|
|
|
| |
PiperOrigin-RevId: 169874059
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 169792510
|
|
|
|
|
|
|
|
|
|
|
| |
In Skylark.java, fix line numbers to start at 1 instead of 2.
In Eval.java, go through maybeTransformException for consistency with expressions, even though no statement nodes use this feature.
In EvalExceptionWithStackTrace, fix style violation (non-consecutive overloads) and add TODO explaining an open issue.
RELNOTES: None
PiperOrigin-RevId: 169769928
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 169753517
|
|
|
|
|
|
| |
that were public because of skylark compilation.
PiperOrigin-RevId: 169739373
|
|
|
|
|
|
|
|
| |
remove all "precomputed values for analysis" from SkyframeExecutor. We use SkyframeExecutor#injectExtraPrecomputedValues these days.
This simplifies logic around when to inject precomputed values, and makes the graph more consistent.
PiperOrigin-RevId: 169733304
|
|
|
|
| |
PiperOrigin-RevId: 169728184
|
|
|
|
|
|
|
| |
nested.
RELNOTES: None
PiperOrigin-RevId: 169723791
|
|
|
|
| |
PiperOrigin-RevId: 169723724
|
|
|
|
|
|
|
|
|
| |
The test was not incorrect before, however it was unfortunate that we were both
expecting an AssertionError and also throwing an AssertionError to signal that
no AssertionError was thrown.
RELNOTES: None
PiperOrigin-RevId: 169721076
|
|
|
|
|
|
|
|
|
| |
and apple_static_library in objc unit tests.
These attributes are deprecated and being removed.
RELNOTES: None.
PiperOrigin-RevId: 169720318
|
|
|
|
|
|
|
|
| |
injected directly, which makes sense, because it's immutable over the lifetime of the server.
Step 3.
PiperOrigin-RevId: 169717587
|
|
|
|
|
|
| |
regarding the integrity of the structure to various operations.
PiperOrigin-RevId: 169715233
|
|
|
|
|
|
|
|
| |
of depending on a precomputed value. BlazeDirectories don't change over the lifetime of the Blaze server, and certainly not over the lifetime of a SkyframeExecutor instance, which already had a reference to them.
Step 2.
PiperOrigin-RevId: 169711443
|
|
|
|
|
|
|
|
| |
depending on a precomputed value. BlazeDirectories don't change over the lifetime of the Blaze server, and certainly not over the lifetime of a SkyframeExecutor instance, which already had a reference to them.
The goal is getting rid of the precomputed value entirely, but since this change necessitated a fair number of testing changes, I'm mailing this out as a first step.
PiperOrigin-RevId: 169705474
|
|
|
|
|
|
|
|
|
|
| |
"AndroidManifest.xml".
aapt requires the manifest to be named "AndroidManifest.xml" (unknown commit)
This allows users to provide manifests with custom names.
RELNOTES: Android rules no longer restrict the manifest file to be named "AndroidManifest.xml".
PiperOrigin-RevId: 169695062
|
|
|
|
|
|
|
| |
and apple_static_library no longer propagate ObjcProvider.
RELNOTES: None.
PiperOrigin-RevId: 169690934
|
|
|
|
|
|
|
| |
Tested manually (with a test that doesn't emit undeclared outputs), and added a test that failed before and passes after the test-setup.sh change.
RELNOTES: N/A
PiperOrigin-RevId: 169687782
|
|
|
|
|
|
|
|
|
| |
Before, linkstamping compile actions were hardcoded in bazel and assumed
gcc/clang and bash. This cl removes gcc/clang assumptions by using feature
configuration.
RELNOTES: None.
PiperOrigin-RevId: 169685949
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 169676866
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolled back commit enforces stricter parameter checks. Will fix and roll forward
This creates several failures on the nightly build of Bazel:
ERROR: /home/ci/workspace/Global/rules_closure-node=linux-x86_64/closure/protobuf/test/BUILD:23:1: no such package '@com_google_protobuf_protoc//': Cannot convert parameter 'url' to type string or sequence of strings, in method download_and_extract(List, string, string, string, string) of 'repository_ctx' and referenced by '//closure/protobuf/test:example_proto_gen'.
ERROR: Analysis of target '//closure/protobuf/test:example_lib' failed; build aborted: no such package '@com_google_protobuf_protoc//': Cannot convert parameter 'url' to type string or sequence of strings, in method download_and_extract(List, string, string, string, string) of 'repository_ctx'.
*** Original change description ***
Check parameter types for methods when multiple types are allowed.
Fixes #3714
RELNOTES: None.
PiperOrigin-RevId: 169669802
|
|
|
|
|
|
|
|
|
|
|
| |
When a timeout occurred, the current test case is interrupted and the others are cancelled. This was not reflected in any way and all tests were reported as success, even if there was a timeout and the tests were cancelled/interrupted.
Also add a status xml attribute to mark if the test was completed, cancelled or interrupted.
Fixes #3763
RELNOTES: None.
PiperOrigin-RevId: 169665622
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The legacy docker_build was removed from bazel_tools
but we need to use it for our integration test so refer
to the one in the main repository.
Also restore the visibility, just excluding it from
bazel_tools is enough and docker_pull needs to call it
from other repository.
Change-Id: I8a8a5781859960030ae996db95fbaf9c54ec596a
PiperOrigin-RevId: 169664916
|
|
|
|
|
|
|
| |
build.lib.actions.SpawnActionContext can import SpawnResult without creating a cyclic dependency.
RELNOTES: None.
PiperOrigin-RevId: 169642267
|
|
|
|
| |
PiperOrigin-RevId: 169631693
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 169624979
|
|
|
|
|
|
|
| |
Introduces the ResourcesZip class to more easily handle processing merged resources.
RELNOTES: None
PiperOrigin-RevId: 169622715
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 169582778
|
|
|
|
|
|
| |
multiple constraint_values from the same constraint_setting (re: #350)
PiperOrigin-RevId: 169577576
|
| |
|