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.

This is for #113454

@drewroengoogle you need to wait until the flutter/engine@59dea4c engine artifacts are published otherwise the tests will fail. I'm re-running them now.

Please avoid doing manual rolls like this. Instead, you can revert a bad roll from the framework tree. Pause the engine -> framework roll, wait for a good build on the engine tree to finish, then re-enable the roller. That way the roll commits contain all the information that the autoroller puts in them.

@zanderso Gotcha, that makes sense! In my head I was trying to get away from the red tree, but I didn't realize it was bad practice to manually roll, so I'll make sure to avoid doing so in the future.