| commit | 9f549dc5e982a11ab967b3d601ba62cde95461c5 | [log] [tgz] |
|---|---|---|
| author | arostovtsev <arostovtsev@google.com> | Mon Feb 14 22:15:58 2022 -0800 |
| committer | fweikert <fwe@google.com> | Thu Feb 17 17:41:54 2022 +0100 |
| tree | 1d440046b68d43880ce0a298dd0df3a251f5ea06 | |
| parent | de3c14da9eba34bed39f4cb34446037813420ae3 [diff] |
Automated rollback of commit 64ac2a81f73ba7b085d0de65f12230814f4151c8. *** Reason for rollback *** See b/219621210 and b/186996003#comment17 *** Original change description *** `TestRunnerAction` now produces a `TestResult` when test lifecycle fails at runtime. Test execution entails running the target's test binary, and even if the binary has been successfully built, the build tool may encounter failures when spawning the test executable process. Previously this scenario did not produce a TestResult or TestSummary BEP event; this is now fixed. Similarly fixed is the scenario where execution fails after spawning the test process successfully. The exception-handling l... PiperOrigin-RevId: 428689515
{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
