| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
More information: https://github.com/junit-team/junit5/issues/531
PiperOrigin-RevId: 186900384
|
|
|
|
|
|
|
| |
This isn't 100% safe, which requires 1:1 type correspondence, but can catch
some errors at compile time.
PiperOrigin-RevId: 186898025
|
|
|
|
| |
PiperOrigin-RevId: 186849562
|
|
|
|
| |
PiperOrigin-RevId: 186837642
|
|
|
|
|
|
|
|
| |
* Deletes a number of CODEC references, now superceded by registry functionality.
* Minimal SkyKeySerializer modifications for correctness, as certain codec changes require
codecs to be in available in the registry.
PiperOrigin-RevId: 186834520
|
|
|
|
|
|
|
| |
See https://blog.bazel.build/2018/01/19/config-parsing-order.html for context on this change.
RELNOTES: --config flags now expand in place by default.
PiperOrigin-RevId: 186831701
|
|
|
|
|
|
|
|
|
|
| |
RuleConfiguredTarget. RuleConfiguredTarget is harder, and will be handled in a follow-up.
Also remove duplicate field from InputFileConfiguredTarget and unused parameter in EnvironmentGroupConfiguredTarget constructor.
Largely punt on FilesetOutputConfiguredTarget for now, but will handle soon.
PiperOrigin-RevId: 186829768
|
|
|
|
|
|
| |
serialize offset table at the cost of some overhead reconstructing the table. Also fewer code changes, although there is a serialization-only method added as a hack.
PiperOrigin-RevId: 186808832
|
|
|
|
|
|
|
|
|
|
| |
Skyframe native Filesets which reference output files.
We were failing to override equality of Artifact to use the artifact owner. See the javadocs on ArtifactSkyKey for more discussion of this.
Before this change, the weak interning of keys done in LegacySkyKey and FilesetEntryKey spuriously matched keys across incremental builds in cases where Artifacts differed only in their owner.
PiperOrigin-RevId: 186805663
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
#doMutatingEvaluation
When multiple keys need to be evaluated, we may schedule keys before informing
progress on done nodes, which can throw InterruptExceptions. If the main thread
is interrupted during #informProgressReceiverThatValueIsDone, then we may not
properly track evaluations which are already scheduled. It could cause threads
continue to run after the main loop is closed.
RELNOTES: None
PiperOrigin-RevId: 186801930
|
|
|
|
|
|
|
|
| |
Replace references to closed-source .bzl files in examples with generic ones. Addresses issue [4321](https://github.com/bazelbuild/bazel/issues/4321).
Closes #4694.
PiperOrigin-RevId: 186800107
|
|
|
|
|
|
|
|
| |
Addresses issue [4637](https://github.com/bazelbuild/bazel/issues/4637) by replacing "else if" with "elif".
Closes #4692.
PiperOrigin-RevId: 186800016
|
|
|
|
|
|
|
|
|
|
| |
email from philwo@.
(i) Only have TimestampGranularityMonitor log the first file of relevance. This reduces log spam, especially in tests, while still maintaining useful information in the logs.
(ii) Don't have ExternalFilesHelper log the fact that it encountered an external file when we're in a unit test or an integration test. Tests, especially bazel tests that use external repositories, tend to involve lots of "external" files.
RELNOTES: None
PiperOrigin-RevId: 186799176
|
|
|
|
|
|
|
| |
AbstractAction had getPrimaryInput() and getPrimaryOutput()
which is why arguments are renamed.
PiperOrigin-RevId: 186795064
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
In particular, use folding menus for Installing and Tutorials.
RELNOTES: None.
PiperOrigin-RevId: 186778997
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Baseline: 00d781ae78a8bd51d3c61b621d79f0bb095aff9e
Cherry picks:
+ ea2d4c475febdbd59ca0e0ba46adc7be759f84e0:
Update stub_finds_runfiles_test to be a real sh_test.
+ d855d8133f4efb73ebd5e82c54a9afb4c7565d46:
java,runfiles: fix bugs in runfiles library
+ 56aeb04a064218b845ecc193d530c341c6ec854d:
Fixing #4585: broken re-execution of orphaned actions.
+ cf3f81aef7c32019d70cbce218a64a03276268f0:
remote: Add support for HTTP Basic Auth
+ 28bd997c1c8793973f63dcae4c22bbae49e7d8b7:
Fixing test-setup.sh occasionally missing stdout/stderr, on
systems where "tail --pid" is supported.
+ 109e4b4dc9e786e3a2d8d7cb245d18320dbe9216:
Automated rollback of commit
7e6837cc1d1aa4259f5c27ba3606b277b5f6c3e9.
+ b3d52b1b6d46a0f23cc91125c1d522e9d13433b4:
Fix incorrect include directories when -no-canonical-prefixes is
passed to clang
+ 3904ac33a983fd8faebba1b52bcac5a3ff942029:
Automated rollback of commit
28bd997c1c8793973f63dcae4c22bbae49e7d8b7.
+ 1001141f0674ff4b611814edcb00a5183680ef4a:
Roll forward of
https://github.com/bazelbuild/bazel/commit/3904ac33a983fd8faebba1
b52bcac5a3ff942029
(https://github.com/bazelbuild/bazel/commit/3904ac33a983fd8faebba
1b52bcac5a3ff942029). Fix #4625 by running the test process in a
sub-shell.
Incompatible changes:
- ctx.fragments.jvm is not available anymore.
New features:
- java,runfiles: You can now depend on
`@bazel_tools//tools/runfiles:java-runfiles` to get a
platform-independent runfiles library for Java. See JavaDoc of
https://github.com/bazelbuild/bazel/blob/master/src/tools/runfiles
/java/com/google/devtools/build/runfiles/Runfiles.java for usage
information.
Important changes:
- The --[no]experimental_disable_jvm command line option is not
supported anymore.
- Allow expanding TreeArtifacts for libraries_to_link
- Proguarded Android binaries can be built with incremental dexing.
- aar_import now supports assets.
- Crash in OutputJar::Close has been fixed
- generator_* attributes are nonconfigurable.
- Introduces --[no]keep_state_after_build
- Add support for merged object files needed for -flto-unit.
- Fix how libraries to link is specified to archiver actions.
- Replace //tools/defaults:android_jar with
@bazel_tools//tools/android:android_jar.
//tools/defaults:android_jar will be removed in a future release.
- java_common.compile supports neverlink
- Resolved an issue where a failure in the remote cache would not
trigger local re-execution of an action.
|
|
|
|
|
| |
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
|