| commit | 242adde185ba10799d03be228466943750e1d5e9 | [log] [tgz] |
|---|---|---|
| author | Googler <cushon@google.com> | Fri Jun 07 10:08:04 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jun 07 10:09:52 2024 -0700 |
| tree | f65da966db1bafedc58c2c9e379f48a6f5deba7c | |
| parent | 80b17f85aa01753947047adb353396e27253db80 [diff] |
Report errors for all files with Error Prone diagnostics, not just the first one This removes logic that was skipping Error Prone of compilations with errors. The intent was to skip analyzing compilations with javac errors, but it also meant that if Error Prone reported an error analyzing a file all subsequent files were skipped. As of unknown commit, `ErrorProneAnalyzer` handles skipping analysis of compilations with errors (and distinguishing between javac and Error Prone errors), so it's safe for JavaBuilder to unconditionally run ErrorProne and let it decided whether or not to proceed. This change also removes some bookkeeping about the number of 'flow' events javac processes and skips, which was used for testing. Since it no longer skips flow events, there isn't a good way to perform the assertion that was done previously. Since that logic was added we have better end to end integration tests for the Error Prone JavaBuilder integration, which reduces the risk of accidentally turning Error Prone off. PiperOrigin-RevId: 641283846 Change-Id: I539f0713879835f031cb13a015b45dfa90e20c24
{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
