This pull request was opened against a branch other than master. Since Flutter pull requests should not normally be opened against branches other than master, I have changed the base to master. If this was intended, you may modify the base back to flutter-3.2-candidate.5. See the Release Process for information about how other branches get updated.

Reviewers: Use caution before merging pull requests to branches other than master, unless this is an intentional hotfix/cherrypick.

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

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.

If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat

See test-exemption from original PR #109428 (comment)

test-exempt: for practical reasons. testing this is likely to cost more than it saves since it's an entirely new ecosystem. #109431 in case we change out minds.

Hey @jmagman can this be merged or luci-flutter test retried as that is the one which is failing currently.

Hey @jmagman can this be merged or luci-flutter test retried as that is the one which is failing currently.

I'm not sure where the luci-flutter failing state is coming from, it should reflect the state of the tree. I filed #110023

Closing, #110045 was merged.