| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 186789569
|
|
|
|
| |
PiperOrigin-RevId: 186789093
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
compilation with @androidndk//:toolchain-libcpp with missing link time files.
This fix needs a way to compare revision numbers, so the type of NdkRelease.majorRevision has been changed to Integer. This also paves the way for r15+ support.
Fixes https://github.com/bazelbuild/bazel/issues/3641
Fixes https://github.com/bazelbuild/bazel/issues/3923
Fixes https://github.com/bazelbuild/bazel/issues/4677
TESTED=bazel test //src/test/shell/bazel/android:android_ndk_integration_test with r11, r12, r13, r14, r15
RELNOTES: Fixed include paths for NDK r13+ llvm-libc++ headers to `ndk/sources/cxx-stl/llvm-libc++/include` and `ndk/sources/cxx-stl/llvm-libc++abi/include`
PiperOrigin-RevId: 186783465
|
|
|
|
|
|
| |
Fixes 4480.
RELNOTES: None.
PiperOrigin-RevId: 186774229
|
|
|
|
| |
PiperOrigin-RevId: 186772981
|
|
|
|
|
|
|
| |
Bazel because the test services APK is no longer installed by default as of unknown commit
RELNOTES: None.
PiperOrigin-RevId: 186772375
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test was failing because it assumed Bazel was
generating a runfiles tree for py_binary.
On Windows, Bazel actually builds a zip file which
contains the py_binary's runfiles tree.
This commit adjusts the tests to assert the zip
file's contents when the test is running on
Windows.
Fixes https://github.com/bazelbuild/bazel/issues/4673
Change-Id: I7544bff6c1866249b8e7982b1a106202d78e10d9
PiperOrigin-RevId: 186770549
|
|
|
|
|
|
| |
different option values between two BuildOptions
PiperOrigin-RevId: 186769975
|
|
|
|
|
| |
Change-Id: Idb0c9fe770cd73c2760bee92997063c4c9b2e94e
PiperOrigin-RevId: 186768436
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Fixed bug due to TransitiveTargetFunction requesting multiple Package dependencies when computing its aspect deps by only applying the optimization to TransitiveTraversalFunction.
*** Original change description ***
Automated rollback of commit cce164aed44aba1de244f0d764cd33a5cc6980b2.
PiperOrigin-RevId: 186766812
|
|
|
|
| |
PiperOrigin-RevId: 186765754
|
|
|
|
|
|
| |
SolibSymlinkAction.
PiperOrigin-RevId: 186765454
|
|
|
|
| |
PiperOrigin-RevId: 186765388
|
|
|
|
|
|
|
| |
Should've been done in https://github.com/bazelbuild/bazel/commit/1a0e2e653c878c36b07880a0d31827fc8ddca353
RELNOTES: None.
PiperOrigin-RevId: 186757061
|
|
|
|
|
|
|
|
| |
Move dealing with coverage related features from CppConfiguration.configurationEnabledFeatures to CcCommon.configureFeatures.
Remove configurationEnabledFeatures.
RELNOTES: None.
PiperOrigin-RevId: 186744803
|
|
|
|
|
|
|
| |
constructor
RELNOTES: None.
PiperOrigin-RevId: 186744674
|
|
|
|
|
|
|
| |
android_local_test should not allow specifying resources and assets on the rule itself. If a user wants to add test specific resources/assets then they should wrap them in an android_library and add it to the deps of the android_local_test.
RELNOTES: None
PiperOrigin-RevId: 186724709
|
|
|
|
|
|
|
| |
reporting that there is a missing 'Args:' section.
RELNOTES: None.
PiperOrigin-RevId: 186717757
|
|
|
|
|
|
| |
This was already fixed in the file set, but was missed in important_output field.
PiperOrigin-RevId: 186711917
|
|
|
|
|
|
|
|
|
| |
consume binary resources.
This functionality is guarded by a flag, --experimental_android_local_test_binary_resources whose default value is false. If the flag is set to true, Bazel will generate the .ap_ and add the path to the .ap_ to the test_config.properties file. Bazel will still generate and pass the raw resources to Robolectric in both cases and so the cue to Robolectric that binary resources should be used is the presence of the path to the .ap_ in the test_config.properties file.
RELNOTES: None
PiperOrigin-RevId: 186708941
|
|
|
|
|
|
| |
now that Bazel no longer passes it.
PiperOrigin-RevId: 186708415
|
|
|
|
|
|
|
| |
android_local_test.
RELNOTES: None
PiperOrigin-RevId: 186699885
|
|
|
|
|
|
|
|
| |
RegisteredExecutionPlatformsFunction, so that errors can be handled as
early as possible.
Change-Id: I2c73a9202d6bb02e04a32c18c4986e1e204aa9d5
PiperOrigin-RevId: 186694303
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 186693205
|
|
|
|
| |
PiperOrigin-RevId: 186691973
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 186690865
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 186679485
|
|
|
|
|
|
|
|
| |
being desugared.
RELNOTES: None.
PiperOrigin-RevId: 186675372
|
|
|
|
|
|
|
| |
workspaces
RELNOTES: None.
PiperOrigin-RevId: 186672083
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 186658512
|
|
|
|
|
|
|
|
|
| |
Fixes #4674.
Tested: https://ci.bazel.build/blue/organizations/jenkins/CR%2Fbazel-tests/detail/bazel-tests/903/pipeline/ (FreeBSD tests pass, failures are unrelated)
Change-Id: Ifc9c5be0cb4d7c877c64fc21632ae8a8c9582d33
PiperOrigin-RevId: 186651937
|
|
|
|
|
|
|
|
|
|
| |
just add it to the interface, and include it in the SpawnResult. This will be used to categorize/aggregate spawns executed by various runners.
Also, minor refinement to the cacheHit property of the SpawnResult with remote execution.
RELNOTES: None
TESTED=presubmit, next cl
PiperOrigin-RevId: 186637978
|
|
|
|
|
|
|
|
|
| |
Because of limitations in Bazel (primarily, Filesets), we always need to filter
on density in execution. As such, remove the deprecated flag that was used to
specify densities that were stamped but not filtered.
RELNOTES: none
PiperOrigin-RevId: 186634496
|
|
|
|
|
|
|
|
| |
These may be reused by configured query, so rather move it early before
consumers starts depending on the old name.
RELNOTES: None
PiperOrigin-RevId: 186633754
|
|
|
|
|
|
| |
actions so that it is non-generic and does not persist a GeneratedExtension, which is hard to serialize.
PiperOrigin-RevId: 186627440
|
|
|
|
|
|
|
|
| |
These may be used to retrieve the ar and as programs associated with
the compiler toolchain.
RELNOTES: None.
PiperOrigin-RevId: 186626548
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 186623143
|
|
|
|
| |
PiperOrigin-RevId: 186617412
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 186617351
|
|
|
|
| |
PiperOrigin-RevId: 186616752
|
|
|
|
|
|
|
|
|
| |
#4683
Fixes second part of failures.
RELNOTES: None.
PiperOrigin-RevId: 186609602
|
|
|
|
|
|
|
|
|
| |
#4683
Fixes one part of failures.
RELNOTES: None.
PiperOrigin-RevId: 186609441
|
|
|
|
|
|
| |
CppLinkAction more suitable for serialization.
PiperOrigin-RevId: 186598828
|
|
|
|
|
|
|
|
|
|
|
|
| |
There's a realpath(3)-like Windows API function
called GetFinalPathNameByHandle{A,W}.
This commit removes JunctionResolver, implements
RealPath using GetFinalPathNameByHandleW, and
replaces JunctionResolver usages with RealPath.
Change-Id: I69efd29c139e957a93496cd75a2db351ed4453e1
PiperOrigin-RevId: 186598195
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note that this dumps the current state in skyframe (which may contain more nodes than you're interested in):
- bazel build --nobuild //interesting:targets
- bazel dump --action_graph=/path/to/file
- printproto --proto2 --raw_protocol_buffer --message=action_graph.ActionGraphContainer --multiline --proto=third_party/bazel/src/main/protobuf/action_graph.proto /path/to/file
We'll add filtering options in a later CL.
RELNOTES[NEW]: Add option to dump the action graph to a file: 'bazel dump --action_graph=/path/to/file'.
PiperOrigin-RevId: 186597930
|
|
|
|
|
|
|
|
|
|
|
| |
Linkstamps were not re-built when only volatile data changed, i.e. when we
modified cc_binary source, linkstamp was not recompiled so we got old
timestamps. The proper behavior is to recompile linkstamp whenever any input to
cc_binary linking action changes. And the implementation in this cl solves this
by adding all linking inputs as inputs to linkstamp compile action.
RELNOTES: None.
PiperOrigin-RevId: 186595143
|
|
|
|
|
|
|
| |
Fixes #3507.
RELNOTES: None.
PiperOrigin-RevId: 186595099
|
|
|
|
|
|
|
|
|
|
| |
While rules that want to be called from different repositories may not
make any assumptions about locations of their dependencies, they still
may embed path obtained via expansion of $(location ...) into their files.
Add tests verifying that this behavior is preserved.
Change-Id: Id71588b4c128c15926d9190db507c9085fd17653
PiperOrigin-RevId: 186591069
|
|
|
|
|
|
|
|
|
|
|
| |
When --run_under is used, the run-under wrapper will be injected in front of the normal test command line. So, it's incorrect to use the beginning of the command line to infer the test name. However, we can always get the underlying test executable with the TEST_BINARY environmental variable.
Rename TEST_NAME to EXE to avoid future confusion.
Fixes https://github.com/bazelbuild/bazel/issues/4588.
Change-Id: I6fd05cca5e5441c13ee16290c4028ec84adec983
PiperOrigin-RevId: 186590311
|
|
|
|
|
|
|
| |
Methods that return NestedSet shouldn't claim they may return duplicates or their return value will have any sort of meaningful order.
Change-Id: I98f92ec6ddbf4d35fea47b12bcd072bb1b0f1e43
PiperOrigin-RevId: 186585490
|