| commit | e6f1d7271cdf61d9dfab3a8b8f34606a3871e3a5 | [log] [tgz] |
|---|---|---|
| author | ajurkowski <ajurkowski@google.com> | Wed Oct 06 08:32:29 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 06 08:34:08 2021 -0700 |
| tree | f1e34ef45f1f427837e0753f7a86b20c8ec0cbf4 | |
| parent | be81bb374e35bc81d36e651fb315d230f40102de [diff] |
Run cleanup and print error log for failed bash tests using `set -e`. The Bash unit test framework relies on tests running `enable_errexit` function to [set up a trap](https://github.com/bazelbuild/bazel/blob/daf5e26c42410fe7708381dd297560d8532ac7e5/src/test/shell/unittest.bash#L94) necessary to run cleanup and print the error log after a failure. Tests which use the canonical `set -euo pipefail` declaration will not set up such trap, therefore they will fail their subshell right after the failure, skipping the cleanup. Add the `ERR` trap automatically so that cleanup happens for all tests using either `enable_errexit` or `set -e*`. PiperOrigin-RevId: 401251154
{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
