[8.9.0] Fix action output handle leak on build/action cancellation (#32058) (#32189) ### Description Close the action execution context when execution throws `InterruptedException`. If closing also throws `IOException`, retain it as a suppressed exception on the original interruption. ### Motivation An interrupted action can leave its output streams open in the long-lived Bazel server. On Windows, a subsequent command using the same server can then fail to delete the action output directory with exit 36. Closing the streams during cancellation removes the dependency on garbage collection to release those handles. Fixes #32050. ### Build API Changes No. ### Checklist - [x] ~I have added tests for the new use cases.~ Can add some tests if wished, but risk of regression is very low imo. - [x] Documentation changes are not needed for this cleanup fix. ### Release Notes RELNOTES: None Closes #32058 COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/32058 from alex-the-third:fix/close-action-context-on-interruption d718505720a1cbd447b025db68b9c17e25a0a222 PiperOrigin-RevId: 1008787258 Change-Id: I687ab83ad4619b8a59e4bb98550193c32c0a0f00 Commit https://github.com/bazelbuild/bazel/commit/3e18cd53b614c1b3172209055f15b2ca2ce5058c Co-authored-by: alex-the-third <139810351+alex-the-third@users.noreply.github.com>
{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
