| commit | 650142fbe290d97e39b702d1dbcdbe126614b927 | [log] [tgz] |
|---|---|---|
| author | Googler <jcater@google.com> | Tue Nov 19 15:42:27 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Nov 19 15:43:36 2024 -0800 |
| tree | df23aeee24177fb475ccfc20b5783179ab25e355 | |
| parent | 4d191f899d1662e6adaf0466517a02b3e663e56f [diff] |
Automated rollback of commit 4515bb6c932ce62c7889cf322319a3b49158acad. *** Reason for rollback *** Trimming CoverageOptions causes and transitions on coverage flags to fail unexpectedly. Starlark transitions have no API to determine if a flag is valid in the current configuration, and because of trimming this may not be a static list. *** Original change description *** Preserve analysis cache through `--run_under` command changes Along the way, also trim `CoverageOptions` as part of the test trimming configuration, matching the logic in `TestConfiguration#SHOULD_INVALIDATE_FOR_OPTION_DIFF`. Also refactor `RunUnder` into a sealed interface implemented by two records. Work towards #3325 PiperOrigin-RevId: 698169645 Change-Id: I9b69ad7c275d6b2d65f1cd5d5ea9941bdc9cf42c
{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
