tree 547b5ca2f8ce0457c0c57807351e3ba46a1e259d
parent d08abc812980310572c61e1d4effbcaa0f191244
author Googler <arostovtsev@google.com> 1747931304 -0700
committer carmenchui@google.com <carmenchui@google.com> 1748454365 +0000
gpgsig -----BEGIN SSH SIGNATURE-----
 U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgKGv7sLM+pEIDOAfTydgJW53atR
 dADtO6XLKIRKDwcvIAAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
 AAAAQLJ4fTC1Lz70sztMPQzQSHBLjMEqqntduFpUBEBA2DYK+iZn8ba3tRl9pIPbu3af6L
 5iHyAapZxJlid43G/oRA4=
 -----END SSH SIGNATURE-----

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