| commit | db4c550691dc448f17027caeeb9aeab337a9bcdd | [log] [tgz] |
|---|---|---|
| author | Googler <adgar@google.com> | Thu Aug 08 11:03:51 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Aug 08 11:05:38 2024 -0700 |
| tree | cceaa9159f68817134184c4a58c3f2024c0d46e8 | |
| parent | df38c206022d89958cef89f3ce64ed9b22c8aa6b [diff] |
Post `TestAttempt`/`TestResult` events when a test can be built but test-exec-config-inputs fail to build. Usually, when a test target can be built, the `TestRunnerAction` will be buildable, but this is not always the case. If the special `exec`-config inputs fail to build, the test action may fail to build, which will only happen in the `test` command. The build tool (and BEP) assume that if a test-type target is buildable, and the command is `test`, then the corresponding `TestAttempt`/`TestResult` events will eventually be posted. This change ensures those events are posted with minimal, correct information indicating the test `FAILED_TO_BUILD`. RELNOTES: BEP will include correct \`TestResult\` and \`TargetSummary\` events when special test inputs like \`$test_runtime\` fail to build. PiperOrigin-RevId: 660904505 Change-Id: Ie44d558be5393ee910e6c4171ac295af2f34b182
{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
