| commit | f40e401a8f6f7cfab2a0e704c2281dd65a1f07cb | [log] [tgz] |
|---|---|---|
| author | ajurkowski <ajurkowski@google.com> | Thu Oct 07 09:09:27 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 07 09:12:26 2021 -0700 |
| tree | 4910118f5322fb837b296b56aeb7b245930ec87b | |
| parent | 503d56eda25b7e2a12431411bfb7ff286d028405 [diff] |
Fix handling of long test names by the bash unit test framework when using `set -eo pipefail`. Bash unit test framework uses `... | head -c 80` to truncate test name, padded with `*`. `head` will read the first 80 bytes and close the file descriptor, consequently, the process stuck on `write(pipe_fd, ...)` will get SIGPIPE and fail. When using `set -eo pipefail`, the exit code will be propagated through the pipe and, consequently, getting the truncated test name will fail. For tests with long names, the name itself will take 80 bytes, therefore `head` will not issue a second `read` and `close` the pipe. This makes the next process which generates the `*` padding run `write` for a pipe with no readers and fail on SIGPIPE. Fix the helper to ignore failures propagated from printing the padded test name. PiperOrigin-RevId: 401527864
{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
