BEP includes a target's built output_groups when another output_group fails. The previous implementation of this feature also included the artifacts successfully built by a failing output_group before it failed. By constructing a new NestedSet<Artifact> without carefully preserving shared structure, the resulting BEP contained NamedSetOfFiles messages with a great many File messages inline, duplicated. The original bug report did not ask for the successfully built outputs from an output_group that has failed outputs. So in reimplementing the feature we exclude any output_group with a failed output. This lets us avoid creating any new NestedSets. Fixes #9413 (again) PiperOrigin-RevId: 290285495
{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:
See CONTRIBUTING.md