It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

Tested, ran dart ./dev/tools/bin/generate_gradle_lockfiles.dart before and after editing exemption list. Did not work before, did work after.

This is test-exempt, though, we really should have a test that we can't get into this state again (i.e. generate_gradle_lockfiles should run in some CI task and report if it would fail, assuming that is safe to do so).