| commit | 4e194efae78280ccfd35f169e4a9333696861318 | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <ci.bazel@gmail.com> | Tue Mar 19 10:03:17 2024 -0400 |
| committer | GitHub <noreply@github.com> | Tue Mar 19 14:03:17 2024 +0000 |
| tree | bb2754187cd3f361d952ae87ca7c791bb1bf4634 | |
| parent | 8aea62148f1338d024601afe8436c1dccab5f01b [diff] |
[7.1.1] Fix sandbox cleanup crashing after server restart (#21733) We try to clean up the sandbox base from previous server instances asynchronously, however sometimes this is not possible due to the old directories being in a different filesystem. This can happen with overlays on Docker after running bazel in different RUN commands. See https://github.com/bazelbuild/bazel/issues/21719 This change fixes the crash by catching the IOException and falling back to synchronous deletion. Fixes #21719. RELNOTES:none Commit https://github.com/bazelbuild/bazel/commit/488b63072687899bdf7607bce949c47097fcd545 PiperOrigin-RevId: 617150522 Change-Id: I82a07ac0ade66cfb1e5732a90a5f3ab4e2e8caa7 Co-authored-by: Googler <plf@google.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
