| commit | 113eaca5862c48797654ae2a3acbb6e15d761485 | [log] [tgz] |
|---|---|---|
| author | Thi Doan <t@thi.im> | Mon Mar 07 05:36:09 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 07 05:37:46 2022 -0800 |
| tree | f6cf6c561b05d2fa879060fb5bc0f1811d982f28 | |
| parent | b1bf9d6c5f85fc4fda0dc48bc3d3e2fe26880867 [diff] |
Do not hide BulkTransferException messages when there were more than one exception Previously, when there were more than one BulkTransferException, it would be reported like this: ``` Executing genrule //:foo failed: Exec failed due to IOException: 221 errors during bulk transfer ``` which didn't include the underlying exception messages. The only case that underlying exceptions were included was when there was only one exception. This change patches the error message to include all the exception messages, which helps diagnose BulkTransferException. Closes #14981. PiperOrigin-RevId: 432921283
{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
