[rbe] Move download locks away from real outputs

The build directory was getting polluted with .dl-lock
(download lock) files, which were inadvertently collected
as remote inputs by reclient.
For some applications like linking, reclient has logic that
globs input from directories, so any instability in the contents
of a directory could result in nondeterministically including
unintended files.
Solution is to move the locks to a completely separate directory,
in this case ".dl-locks".

Fixed: 394155554
Change-Id: I9a41eb7506a3b44f708d53400a28ec7ede20da13
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1198864
Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>
Fuchsia-Auto-Submit: David Fang <fangism@google.com>
Reviewed-by: Aaron Wood <aaronwood@google.com>
1 file changed
tree: 9f2af02fdaf095529414d6c96ee9497ce422443b
  1. .helix/
  2. boards/
  3. build/
  4. bundles/
  5. docs/
  6. examples/
  7. infra/
  8. products/
  9. scripts/
  10. sdk/
  11. src/
  12. third_party/
  13. tools/
  14. zircon/
  15. .clang-format
  16. .clang-tidy
  17. .editorconfig
  18. .git-blame-ignore-revs
  19. .gitattributes
  20. .gitignore
  21. .gitmodules
  22. .gn
  23. .ignore
  24. analysis_options.yaml
  25. AUTHORS
  26. BUILD.gn
  27. CODE_OF_CONDUCT.md
  28. CONTRIBUTING.md
  29. fuchsia.code-workspace
  30. LICENSE
  31. OWNERS
  32. PATENTS
  33. pyproject.toml
  34. pyrightconfig.json
  35. README.md
  36. rustfmt.toml
  37. shac.star
  38. shac.textproto
README.md

Fuchsia

What is Fuchsia?

Fuchsia is an open source, general purpose operating system supporting modern 64-bit Intel and ARM processors.

We expect everyone interacting with our project to respect our code of conduct.

Read more about Fuchsia's principles.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See fuchsia.dev.