[10.0.0] Report the failure of a shared download with the input of each caller (#31468) (#31689) ### Description Downloads of remote files are deduplicated by the path of the file they write, which different inputs can resolve to, e.g. two symlinks to the same file. If such a download failed because the file was no longer available in the remote cache, every caller received the failure that names the input of the caller that started the download. Each caller now receives a failure that names its own input. ### Motivation An action that joined a download through a different input couldn't find the reported input among its own and failed instead of reporting a lost input, which could have been recovered. Work towards #31456 ### Build API Changes No ### Release Notes RELNOTES: None Closes #31468 COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/31468 from fmeum:prefetch-shared-download-failures a6358e19a728b99247f69d3a9d2b211ceb624efa PiperOrigin-RevId: 996373669 Change-Id: Ifa3c460b188d3014759a0fcab332af785045c921 Commit https://github.com/bazelbuild/bazel/commit/c646df338059abc82824283d9740d874b67f7c13 Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
{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.
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
