[9.4.0] Download top-level source files also without merged analysis and execution (#31489) (#31636) ### Description The handler that downloads the outputs of top-level targets at the end of a build is now registered regardless of whether analysis and execution are merged. ### Motivation Without `--experimental_merged_skyframe_analysis_execution`, the outputs of top-level targets are downloaded when the actions that produce them are finalized. A source file of a repo that is served from the remote repo contents cache has no such action, so it was never downloaded: `bazel run @my_repo//:tool.sh` reported a successful build and then failed to execute the file. `testRunSourceExecutableWithoutMergedAnalysisAndExecution` reproduces this. For derived outputs, the handler finds the files already downloaded and only has to check their presence. Work towards #31456 ### Build API Changes No ### Release Notes RELNOTES: None Closes #31489 COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/31489 from fmeum:rrcc-toplevel-source-outputs 22fdd51f0121ec6e53384c3e9e066496f359060d PiperOrigin-RevId: 995700533 Change-Id: Ie7e4b7b6c0c2947b21845c75ccccc3f64a946e31 Commit https://github.com/bazelbuild/bazel/commit/7cb306b47fad1c353208822e37f9e78902e5e39f Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im> Co-authored-by: Ian (Hee) Cha <heec@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