Let the remote branch finish when the local branch lost an input (#31536) ### Description When the local branch fails with a `LostInputsExecException`, which arises while its execution is set up, before a spawn runs or the output lock is taken, it no longer cancels the remote branch. `DynamicSpawnStrategy.waitBranches` awaits the remote branch in that case and returns its result; the lost input is reported, with the remote branch's failure attached as a suppressed exception, only if the remote branch doesn't produce a result either. ### Motivation With dynamic execution, a source file of a repository that was lost from the remote cache made the local branch fail during input prefetching, which cancelled a remote branch that had a valid action result for the same spawn and needed none of the file's bytes. That forced a repository refetch, which fails when the file's origin is unavailable, although remote-only execution succeeds. Reported in https://github.com/bazelbuild/bazel/pull/31452#issuecomment-5974592151. Work towards #31456 ### Build API Changes No ### Release Notes RELNOTES: None Closes #31536 COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/31536 from fmeum:dynamic-lost-inputs-remote-branch d99ccd91413c64a7c1c8bffc1a8d2643a79b8422 PiperOrigin-RevId: 999646410 Change-Id: I0aa9159a5b1ef68201055f1c03d2828348f75513
{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
