| commit | bbc390fe5c5290c76f804c4823cb1ad362729adf | [log] [tgz] |
|---|---|---|
| author | Googler <arostovtsev@google.com> | Thu May 22 09:28:24 2025 -0700 |
| committer | carmenchui@google.com <carmenchui@google.com> | Wed May 28 17:46:05 2025 +0000 |
| tree | 547b5ca2f8ce0457c0c57807351e3ba46a1e259d | |
| parent | d08abc812980310572c61e1d4effbcaa0f191244 [diff] |
Correctly handle failing finalizers; allow unexpanded finalizers in a package which contains errors If the evaluation of a package threw an EvalException, it is possible and legal for some finalizers to be left unexpanded. Moreover, we shouldn't try to expand finalizers in a package that's already in error, just as we already stop evaluating top-level code and non-finalizer macros after an earlier step in package evaluation throws. Fixes ISE introduced by https://github.com/bazelbuild/bazel/commit/11c38261667b9976b7bd08f9f05c8a735d65f8e2 PiperOrigin-RevId: 761997199 Change-Id: I2a1576b0f112ef20e1f71a0b6e3b774fba69b7c1
{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
