| commit | 830d4649b42451161adbdf907d9935e648f17d8c | [log] [tgz] |
|---|---|---|
| author | Matt Clarkson <matthew.clarkson@arm.com> | Tue May 10 05:21:05 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue May 10 05:22:59 2022 -0700 |
| tree | 6e98f260963d7b7c4c6b4a2203a5eaa6f8b8682a | |
| parent | 83ca7d1d7533e610e1dec7ecdcf35a0927087041 [diff] |
Export `BAZEL_TEST=1` for `bazel test` executables [Catch2][catch2] has [learnt][pr2399] how to output JUnit to the `XML_OUTPUT_FILE`. However, the upstream developers [felt][comment] that `XML_OUTPUT_FILE` is too generic to blanket enable JUnit output to the file as there are various XML reporters for Catch2. This patch enables exporting `BAZEL_TEST` environment variable so that Catch2 can enable JUnit output support unconditionally in their build when both `BAZEL_TEST` _and_ `XML_OUTPUT_FILE` are available. [catch2]: https://github.com/catchorg/Catch2 [pr2399]: https://github.com/catchorg/Catch2/pull/2399 [comment]: https://github.com/catchorg/Catch2/pull/2399#issuecomment-1092965791 Closes #15393. PiperOrigin-RevId: 447706388
{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
