commit | a84aea851c25e05f8118070c9585264a8512598b | [log] [tgz] |
---|---|---|
author | Tiago Quelhas <tjgq@google.com> | Thu Nov 16 18:09:08 2023 +0100 |
committer | GitHub <noreply@github.com> | Thu Nov 16 17:09:08 2023 +0000 |
tree | 7dbab5573b656c05096401468e8a9efde690f944 | |
parent | 61fa9331099dbc73df4b9d51ad1143f23369d8a2 [diff] |
[7.0.0] Print $TEST_UNDECLARED_OUTPUTS_ZIP failure reason (#20223) Zipping up the `$TEST_UNDECLARED_OUTPUTS_DIR` can fail -- for example if `zip` is not installed. This PR improves the printed message to include the actual failure reason. It's easy to test this manually with a brutal `sudo mv /bin/zip /bin/zip.backup`: The old message looked like `Could not create /home/user/.cache/bazel/_bazel_laltenmueller/5f48ff965103b174f3c248651ebad24d/sandbox/linux-sandbox/1/execroot/repo/bazel-out/k8-fastbuild/testlogs/path/to/package/test/run_2_of_2/test.outputs/outputs.zip": zip not found or failed` The new message looks like `Could not create "/home/user/.cache/bazel/_bazel_laltenmueller/5f48ff965103b174f3c248651ebad24d/sandbox/linux-sandbox/1/execroot/repo/bazel-out/k8-fastbuild/testlogs/path/to/package/test/run_1_of_2/test.outputs/outputs.zip": external/bazel_tools/tools/test/test-setup.sh: line 430: zip: command not found` Closes #18929. PiperOrigin-RevId: 582906687 Change-Id: I86e87ce2d0693286fc84fd55ae520783f546189f Co-authored-by: Laurenz Altenmller <laurenz.altenmueller@fernride.com>
{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