| commit | cc4036e2ba975066651d138f777b33bb7b50aaee | [log] [tgz] |
|---|---|---|
| author | adgar <adgar@google.com> | Fri Jan 07 14:30:53 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jan 07 14:32:24 2022 -0800 |
| tree | 3323fab4b2b206df43a2e93a8f15fb5311bff608 | |
| parent | feda6e16f14a4d8ce7fa723191e0072170850d7b [diff] |
Add missing BEP conversion for BlazeTestStatus.FAILED_TO_BUILD. The FAILED_TO_BUILD enum value has been present since the enum was introduced in July 2014. The BEP conversion has been missing since BEP was introduced. In general, FAILED_TO_BUILD is a rare BlazeTestStatus because if a test-type target fails its build analysis or execution, we do not produce a BlazeTestStatus and do not produce TestResult or TestSummary BEP events. It is possible however for this enum value to be produced at test execution time in exceptional circumstances. Keeping the two enums in sync is also simply good practice. RELNOTES: None. PiperOrigin-RevId: 420371401
{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
