Allow materializer rules to be tested under failure conditions in analysis tests. Previously, DependencyProducer required MaterializedDepsInfo to always be present for all materializer targets. This caused bazel to crash on a precondition check when a materializer rule called `fail()` under an analysis test that expects failure, allowing it to return no MaterializedDepsInfo and bypassing the check in StarlarkRuleConfiguredTargetUtil. Futhermore, do not remove failing materializer targets from the deps under an analysis test that expects failure so that test can observe the AnalysisFailureInfo provider. PiperOrigin-RevId: 869873775 Change-Id: I3b88588d03771fe2dbcd40059cb7c6ede46f9b99
{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.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
