commit | c92d0e1c0bfbc2573104ff09d8dec282e85cafa1 | [log] [tgz] |
---|---|---|
author | Ken Micklas <kmicklas@uber.com> | Wed Aug 24 09:55:24 2022 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Aug 24 09:56:24 2022 -0700 |
tree | bf59492ee6ed6e9b9ab6d0090ab66501455e8698 | |
parent | a78ab9dc08dec7b6706f0b585b83dff95ccaba07 [diff] |
Include exception message for "Source forest creation failed" error We experienced this error from integration tests which failed to clean up after themselves and left write-protected files behind. This is just a small messaging improvement which would have made finding the root cause easier. The change here is analogous to this error: https://github.com/bazelbuild/bazel/blob/d1820a75ea3eb182ef2c2319bb77be19c4113a47/src/main/java/com/google/devtools/build/lib/buildtool/ExecutionTool.java#L875 Closes #16071. PiperOrigin-RevId: 469754461 Change-Id: I23649844178f6c5b4c2c016903289ac043f2c230
{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