Updates BuildViewTestCase.invalidatePackages() to also invalidate

configurations.

This is important for dynamic configurations.

invalidatePackages() invalidates every file. This includes CROSSTOOL,
which the CppConfiguration fragment depends on.

For static configurations, this doesn't matter because all configurations
and their fragments are pre-computed at the beginning of the build (or
in the case of tests before the test case starts).

For dynamic configurations, the configuration can get custom-created
each configured target. When that happens after invalidatePackages,
a new CppConfiguration instance gets created. This can impact code
like CcLibraryHelper.addDeps(), which assumes equality (CppConfiguration
has no .equals() method).

Normally that's not a problem because the same CppConfiguration instance
is used for every target in the post-invalidatePackages() graph. But
host configurations break this: we keep a non-Skyframe host config cache
in SkyframeBuildView.hostConfigurationCache. Without this change, it
doesn't get cleared out, so it keeps old pre-invalidation references that
under certain circumstances get applied to post-invalidation targets.

--
MOS_MIGRATED_REVID=125379342

0 files changed, 0 insertions, 0 deletions