| commit | 3448371f7c030dceed7c84599ae85d27208eb1a5 | [log] [tgz] |
|---|---|---|
| author | Googler <lberki@google.com> | Tue Jan 30 05:04:33 2024 -0800 |
| committer | fweikert <fwe@google.com> | Fri Feb 09 19:36:32 2024 +0100 |
| tree | 45c8e64b99346b600c4a0cd46cc731727b1ebf2b | |
| parent | ca728739071c78c67b5d251c7be4b9ba7c17b225 [diff] |
Only cache runfiles mappings of tests if they have more than one shard or run per test. This is an attempt to fix Bazel excessively OOMing at Google. This change was behavior was caused by https://github.com/bazelbuild/bazel/commit/08df6f1ebeaccb43d3aac1058f8d9e28e11acd2b where I believed that the soft reference makes the caching a no-op wrt. memory use. This does not quite reinstate the same behavior as before https://github.com/bazelbuild/bazel/commit/08df6f1ebeaccb43d3aac1058f8d9e28e11acd2b: firstly, it doesn't take --test_sharding_strategy into account (it could, but I would have had to make TestShardingStrategy public instead of package-internal) and it doesn't garbage collect the soft reference after the all actions of a given test target finish running. It's still an improvement, though, and profiling shows that it has a good chance of fixing the problem. RELNOTES: None. PiperOrigin-RevId: 602689571 Change-Id: Ib68c1b88bf47898ae8a59866447d7790bb6eceee
{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
