commit | 0b62df09609c9c29ead2f955e86e076c84da86bf | [log] [tgz] |
---|---|---|
author | Googler <lberki@google.com> | Wed Apr 12 01:38:21 2023 -0700 |
committer | fweikert <fwe@google.com> | Tue Apr 18 18:43:09 2023 +0200 |
tree | c5d8552774d1f3c0dab1e68f33343fd365c63b73 | |
parent | 5ab5d80e08bd42b056403c12f2d1f7be4996e3d4 [diff] |
Automated rollback of commit 4a2e51b3d7b7a27d243e8cc233d60fbbaeeb6190. *** Reason for rollback *** Breaks targets on the nightly TGP. Reproduction: blaze build //third_party/bazel_rules/rules_kotlin/tests/android/java/com/google/jni:AndroidJniTest --compilation_mode=opt --flaky_test_attempts=2 --fat_apk_cpu=x86 --android_platforms=//buildenv/platforms/android:x86 --incompatible_enable_android_toolchain_resolution=1 --collect_code_coverage=1 --instrumentation_filter=//java/com/google/android/samples/apps/topeka[/:],//third_party/bazel_rules/rules_kotlin[/:],//tools/build_defs/kotlin[/:] TGP link: [] *** Original change description *** Make `getPrimaryOutput()` always return the first artifact in `getOutputs()`. This is already the case everywhere except `CppCompileAction` but was not documented, leading to `SpawnAction` unnecessarily storing a field for the primary output when it's already just the first element in its outputs. This change saves 8 bytes per `SpawnAction` and `GenRuleAction`, and moves other `SpawnAction` subclasses closer to an 8-byte threshold. `CppCompileAction` had been using the coverage artifact (if pr *** RELNOTES: None. PiperOrigin-RevId: 523634597 Change-Id: I0aa70851fe4d403afabc56e808546d6638a9f2b7
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md