[9.3.0] Bust caches for rewound actions (#31300) (#31420) ### Description When an action is rewound, it needs to bust both intra-build Bazel caches as well as remote caches to ensure that the rewinding is effective: * When a remote cache doesn't verify that the `ActionResult`s it returns reference existing CAS blobs, rewinding can get into a loop and fail when the maximum number of retries is exhausted. `knownMissingCasDigests` handled this for build rewinding, but by design can't accommodate intra-build recovery (as observed in https://github.com/bazelbuild/bazel/pull/31251). Instead, just disable remote caching for rewound actions until a better signal is available (see the TODOs and https://github.com/bazelbuild/remote-apis/pull/386). * Bazel's upload deduplication and caching could result in an action that's been rewound multiple times not reuploading its local outputs. Such caches and deduplication are now ignored for rewound actions. `LostInputsEvent` and `knownMissingCasDigests` remain in use only for the legacy whole-invocation retry path when action rewinding is disabled. The extra wiring required to propagate `LostInputsEvent` for a rewound action has been removed. ### Motivation ### Build API Changes No ### Checklist - [x] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). ### Release Notes RELNOTES: None Closes #31300 COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/31300 from fmeum:fix-missing-cas-digest-lifecycle 9055476e5fb1a2af007bb6d33077af4b7099fe44 PiperOrigin-RevId: 990587446 Change-Id: I8e14f5bea2fbfb584756e7e16ccd925f8d57c945 <!-- Thank you for contributing to Bazel! Please read the contribution guidelines: https://bazel.build/contribute --> ### Description <!-- Please provide a brief summary of the changes in this PR. --> ### Motivation <!-- Why is this change important? Does it fix a specific bug or add a new feature? If this PR fixes an existing issue, please link it here (e.g. "Fixes #1234"). --> ### Build API Changes <!-- Does this PR affect the Build API? (e.g. Starlark API, providers, command-line flags, native rules) If yes, please answer the following: 1. Has this been discussed in a design doc or issue? (Please link it) 2. Is the change backward compatible? 3. If it's a breaking change, what is the migration plan? --> No ### Checklist - [ ] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). ### Release Notes <!-- If this is a new feature, please add 'RELNOTES[NEW]: <description>' here. If this is a breaking change, please add 'RELNOTES[INC]: <reason>' here. If this change should be mentioned in release notes, please add 'RELNOTES: <reason>' here. --> RELNOTES: None Commit https://github.com/bazelbuild/bazel/commit/f653dd6d08351de86caafc684af6ed6abc975df8 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.
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
