Delay creation of params files until we know where the writable execroot is.

When using workers or sandboxes, the output tree is not locked until the
spawn completes execution.  However, some virtual inputs, like params files,
have to be materialized before running the spawn.

The previous code was materializing these files directly into the output
tree without previously grabbing the dynamic execution lock, causing trouble.

To fix this, postpone the creation of these files until we know where the
writable execroot for a spawn is (which, when using workers or sandboxes is
in a location separate from the actual execroot).

This fix is gated behind --experimental_delay_virtual_input_materialization
so that we can roll it out separately from a release given the limited testing
we can do on builds that do local execution.  I'll remove the old code paths
once we have flipped the flag.

Problem diagnosed by felly@.

RELNOTES: None.
PiperOrigin-RevId: 301849551
14 files changed
tree: fa5c8abe6f67b9fc0b80991947d98ad6a91f576c
  1. .bazelci/
  2. examples/
  3. scripts/
  4. site/
  5. src/
  6. third_party/
  7. tools/
  8. .bazelrc
  9. .gitattributes
  10. .gitignore
  11. AUTHORS
  12. BUILD
  13. CHANGELOG.md
  14. CODEOWNERS
  15. combine_distfiles.py
  16. combine_distfiles_to_tar.sh
  17. compile.sh
  18. CONTRIBUTING.md
  19. CONTRIBUTORS
  20. distdir.bzl
  21. ISSUE_TEMPLATE.md
  22. LICENSE
  23. README.md
  24. WORKSPACE
README.md

Bazel

{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.

Getting Started

Documentation

Contributing to Bazel

See CONTRIBUTING.md

Build status