Create a clear boundary between action conflict and other analysis error handling. ...and as a result, simplifying the error parsing code for analysis. Analysis error processing [1] had a rather complex pattern: we go through the results and return a ViewCreationFailedException to be thrown in case of --nokeep_going. This is to accommodate the complex legacy order of throwing action conflict exceptions & other analysis exceptions [2]. We no longer see a strong reason to support this behavior and simplifying the code would be more desirable. The error handling method would now simply throw the first exception found in case of --nokeep_going. This also brings it closer to how execution exceptions are handled. User Visible Change: in case of --nokeep_going, non action conflict errors are thrown first. [1] https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java;l=1032;drc=3cd5f8411a22341c5c964cfd03166a3bdc267bfc [2] https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java;l=532-539;drc=095f1e24ae3fa0860bdda5af7befe74c1123a078 PiperOrigin-RevId: 430994018
{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
