| commit | f95fda5df55b1618ef54f0e2dda8607e4f9b919d | [log] [tgz] |
|---|---|---|
| author | larsrc <larsrc@google.com> | Wed Mar 09 01:42:43 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Mar 09 01:44:06 2022 -0800 |
| tree | 606025bf06ee3c4fe81903259ce94f545dcf34df | |
| parent | 828f660dce70e62e74f737dca5ab27fbc5490199 [diff] |
Propagate systems errors back out of BazelJavaBuilder and shut down the worker when they happen. Bad handling of system errors in BazelJavaBuilder led to a more systematic handling of shutting down WorkRequestHandler in general. If a request thread throws an uncaught exception or there's an IOException talking to the server, the worker gets shut down. When shutting down the worker, it interrupts all outstanding threads. It doesn't currently wait to see if the threads actually stop and try to forcefully stop them. If that turns out to be necessary, we should call Thread.suspend() then Thread.stop() for each of the active requests at the end of processRequest(). Those APIs are deprecated, though, so I would rather not use them unless necessary. Because exception handling changed, I also had to change the tests to be more explicit about when the message processor stops. PiperOrigin-RevId: 433420732
{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
