| commit | ea35fc831d7774c95719cbdce8eb2aaabb00b19a | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <ci.bazel@gmail.com> | Mon Oct 28 19:44:54 2024 +0100 |
| committer | GitHub <noreply@github.com> | Mon Oct 28 18:44:54 2024 +0000 |
| tree | a21d69efa2db475b2ab676d84cbd6575c68ad7cb | |
| parent | 253d11fb8632951e4a94fbe01aa1ba6c8aa40bf9 [diff] |
[8.0.0] Prevent excessive thread creation in disk cache garbage collection (#24113) Fixes https://github.com/bazelbuild/bazel/issues/24098 With this change the disk cache garbage collection works correctly: ``` 241027 09:06:34.732:I 681 [com.google.devtools.build.lib.remote.disk.DiskCacheGarbageCollectorIdleTask.run] Disk cache garbage collection started 241027 09:07:06.123:I 681 [com.google.devtools.build.lib.remote.disk.DiskCacheGarbageCollectorIdleTask.run] Deleted 190243 of 446229 files, reclaimed 5.4 GiB of 15.4 GiB ``` Closes #24099. PiperOrigin-RevId: 690652512 Change-Id: Ie8d1fa6b2afb0bd5bd85fdb6835871023a64ad24 Commit https://github.com/bazelbuild/bazel/commit/374658377f662701f1e92f757090949fdd0da1ab Co-authored-by: Roman Salvador <rsalvador@salesforce.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
