Fix non-deterministic NPE in
`SkyframeActionExecutor::createAndCheckForSymlinks`.

Before we execute an action, we create a directory structure for its outputs.
For each output, we must ensure each ancestor directory exists, up to the
output root. Some of those directories overlap across actions (e.g. `//foo:a`
and `//foo:b` both will output under `foo` directory), which is why we have a
shared cache to avoid stats for those.

The logic resolving ancestor directories first [adds the root to
`knownDirectories`
map](https://github.com/bazelbuild/bazel/blob/e2ae73fe16cbedf095b9e6d5687b06ecf765d794/src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java#L1368-L1370)
and then, for each directory, [walks it up until it finds
an entry in the
map](https://github.com/bazelbuild/bazel/blob/e2ae73fe16cbedf095b9e6d5687b06ecf765d794/src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java#L1376).
That is sound for a regular map since every directory is under the root. The
problem is that the [`knownDirectories` map is actually a
cache](https://github.com/bazelbuild/bazel/blob/e2ae73fe16cbedf095b9e6d5687b06ecf765d794/src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java#L299-L303),
subject to eviction. If that happens for the root, then the loop will
continue until `PathFramgent::getParentDirectory` returns null and NPE.

Fix the check to compare paths to the root as we walk ancestors of paths. This
way checking the cache is just an optimization with no bearing on correctness.

PiperOrigin-RevId: 375131623
2 files changed
tree: c6c85a8bd7e3007254284d33167638b7f5d5856b
  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. CODEBASE.md
  15. CODEOWNERS
  16. combine_distfiles.py
  17. combine_distfiles_to_tar.sh
  18. compile.sh
  19. CONTRIBUTING.md
  20. CONTRIBUTORS
  21. distdir.bzl
  22. distdir_deps.bzl
  23. ISSUE_TEMPLATE.md
  24. LICENSE
  25. README.md
  26. 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