Google Git
Sign in
bazel / bazel / 020dd5f1ee9c2c388644dbcd45cda4ebf6b42876
commit020dd5f1ee9c2c388644dbcd45cda4ebf6b42876[log] [tgz]
authorarostovtsev <arostovtsev@google.com>Wed Apr 14 14:05:41 2021 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Apr 14 14:07:07 2021 -0700
treea076a1b3f1edbf91ce20c664845880da52b64186
parentcb37ecb70ac08b15e0371421f498a6e551ab875a [diff]
Propagate analysis-time aspect failures in AnalysisFailureInfo when using --allow_analysis_failures

When using --allow_analysis_failures, if an aspect implementation function
fails, bazel currently asserts because AspectFunction does not expect to get a
null ConfiguredAspect.

Instead, similarly to what we do for analysis-time failures in rules when using
--allow_analysis_failures, we want to create a special "errored aspect" and
propagate the failures in AnalysisFailureInfo. That way, the failures can be
tested for in bazel-skylib's analysistest with `expect_failure = True`.

RELNOTES: When using --allow_analysis_failures (for example, via bazel-skylib's
analysistest with `expect_failure = True`), analysis-time failures in aspect
implementation functions will now be propagated and saved in
AnalysisFailureInfo, just like analysis-time failures in rules.
PiperOrigin-RevId: 368504346
3 files changed
tree: a076a1b3f1edbf91ce20c664845880da52b64186
  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