| commit | 10d30842b1018e4f7d41358c0494466cf56e4c34 | [log] [tgz] |
|---|---|---|
| author | ajurkowski <ajurkowski@google.com> | Tue Dec 07 15:28:00 2021 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Dec 07 15:29:35 2021 -0800 |
| tree | 9578de120b05000e87a5a59629e83c6e524528ec | |
| parent | d0fde13454a71355b7695922c2179d8756b4632f [diff] |
Do not leave uncaught exception handler past tests derived from `BuildIntegrationTestCase`. In https://github.com/bazelbuild/bazel/commit/882321bd2cd126e586cb555e7f4ae535d965ec3d, I added a default exception handler for uncaught exceptions for parity with Bash-based tests. This change will leave the handler behind and potentially pollute tests which don't expect it. Make sure to clean the uncaught exception handler after after each test using `BuildIntegrationTestCase`, otherwise we [can leave an interrupted flag behind](https://github.com/bazelbuild/bazel/blob/d0fde13454a71355b7695922c2179d8756b4632f/src/main/java/com/google/devtools/build/lib/runtime/CommandEnvironment.java#L344). PiperOrigin-RevId: 414840674
{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
