Fix error reporting omission.

The problem with error reporting was caused by:
- The error being printed to stderr in ActionExecutionFunction#checkCacheAndExecuteIfNeeded
- ActionExecutionFunction#accumulateInputs of a higher-level action throws ActionExecutionException and halts the evaluation before lower-level actions that are covered by ArtifactNestedSetKeys have the chance to be evaluated by Skyframe (hence printing their errors).

To fix this, we need to make sure the transitive ArtifactNestedSetKeys get evaluated i.e. checking env.valuesMissing in ActionExecutionFunction after evaluating the inputs. However, checking for missing values should only be done after the handling of all exceptions (if any). This CL refactors accumulateInputs to separate the error-handling portion from the input-accumulation portion. We can then check for missing values after handling the exceptions (if any), and before accessing the NSOS map for input accumulation.

Significant changes:
- New ArtifactNestedSetEvalException: bundles together individual exceptions from children, to be handled in ActionExecutionFunction.
- Refactoring of accumulateInputs: separate error-handling and input-accumulation.
- The NSOS map now no longer hold ValueOrException but instead: Map<SkyKey, SkyValue>

This change is flag-guarded behind --experimental_nsos_eval_keys_as_one_group.

RELNOTES: None
PiperOrigin-RevId: 314293281
4 files changed
tree: 0347e3cc026836aeb1437666a30fb62c2813ae09
  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