| commit | c237e02e81d35e9ecf72b52a316383448ba22b1a | [log] [tgz] |
|---|---|---|
| author | Ulrik Falklof <ulrik.falklof@ericsson.com> | Wed Oct 15 06:09:24 2025 -0700 |
| committer | Tiago Quelhas <tjgq@google.com> | Thu Oct 16 09:35:34 2025 +0200 |
| tree | 280d26fb5724202d55020b69eb80ef3a421fe7bb | |
| parent | acbe1a5468b49ef42210546bcacab656a20e7413 [diff] |
[8.5.0] Do not download in-memory outputs The documentation for `--experimental_inmemory_dotd_files` and `--experimental_inmemory_jdeps_files` states '_...instead of being written to disk_', but the files were actually written to both memory and disk (unless combined with BwoB). This caused two problems: 1) Unnecessary overhead from **remotely downloading** all in-memory files **twice**. 2) Paradoxically **reduced robustness of `--remote_download_all`**: that flag normally increases Bazel’s resilience to remote cache issues, but because these outputs were kept in memory instead of being written to disk by RemoteSpawnCache.lookup (which handles cache issues gracefully), action finalization treated them as missing on disk and attempted a more fragile download, increasing the risk for "_unable to finalize action_" failures (see #22387). This change ensures that in-memory files are kept exclusively in memory and are not written to disk. This aligns with the documentation and addresses both problems. Fixes #22387 Closes #26898. PiperOrigin-RevId: 819717587 Change-Id: If658fcf239b0923450fdf394556268caaeded247
{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
