| commit | 788d00e7eec408930e2b895d013c4cb75ea23e28 | [log] [tgz] |
|---|---|---|
| author | Benjamin Lee <ben@ben.cm> | Sun Aug 27 22:15:14 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Sun Aug 27 22:16:35 2023 -0700 |
| tree | fced398514553253f0c43efebbc5db15619c9bd4 | |
| parent | 81d12dbfa24d047453e96e10eedabc9126b108b4 [diff] |
Avoid writing D8 info and error messages directly to the Bazel console This pull request provides a custom `DiagnosticsHandler` implementation that redirects info and warning messages to the original `System#err` stream so that the noisy D8 messages are written to the worker log file instead of directly to the console. In addition this PR also removes the custom system stream redirection, and instead uses the baked in `WorkerIO` implementation that automatically wraps the system stream for us that was added here https://github.com/bazelbuild/bazel/pull/14201. https://github.com/bazelbuild/bazel/issues/17647 Closes #17648. PiperOrigin-RevId: 560600558 Change-Id: I9d2d162b62fe5dfd00e8614ba73caf1cac5f02d7
{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
