[9.1.1] Cache CAS interactions at lower layer to fix lost input handling (#29677) The error handling for uploads in `UploadTask` depends on the exec path of the uploaded file, which wasn't part of the `casUploadCache` cache key. Fix this by moving deduplication logic for CAS uploads and `FindMissing` calls into `RemoteCacheClient`. Avoids spurious Bazel failures caused by lost inputs that can't be recovered from via build or action rewinding due to `CacheNotFoundException` being marked with exec paths of inputs to concurrent actions (see the new test case). No - [x] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). RELNOTES: Fixed an issue that caused Bazel to fail on a lost input even with build or action rewinding enabled. Closes https://github.com/bazelbuild/bazel/pull/29551. PiperOrigin-RevId: 922775351 Change-Id: Ia22580325c3bc92b56d202e5c24d3630fc8c27a0 (cherry picked from commit https://github.com/bazelbuild/bazel/commit/100272284dde7a7504e7581604ddcf826788b6c8, includes https://github.com/bazelbuild/bazel/commit/5572634408f7ead56ebb544ab037ffa125a0154b and https://github.com/bazelbuild/bazel/commit/8f5af363182885e08179d47313d417e40fa922d5) Fixes #29575 --------- Co-authored-by: tjgq <tjgq@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
