Fix some bugs in SkyframeErrorProcessor. 1. Only send AnalysisFailureEvent in SkyframeErrorProcessor if the error is analysis-related. AnalysisFailureEvent tells us that the analysis of a top level target failed and it wasn't executed at all. It's wrong to also send this if the error is execution-related. 2. Handle an execution error originating from an Aspect. This was an oversight when we introduced this combined mode of error handling for Skyframe. Added a test for this scenario. PiperOrigin-RevId: 446950178
{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
