This repository was archived by the owner on Feb 25, 2025. It is now read-only.
[macOS] Fix arm64 floating-point test failure #41228
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FlutterMutatorViewTest.TransformedFrameIsCorrect and FlutterMutatorViewTest.RoundRectClipsToPath both apply transforms then do exact comparisons on the resulting 4x4 matrices of CGFloat values.
There are very small differences between the elements in the resulting matrices, on the order of 1e-15, depending on the CPU architecture on which the floating point operations were run.
Similar to elsewhere in the framework and engine, we now perform floating point equality tests within some small error bound -- I've arbitrarily selected 1e-10.
Issue: flutter/flutter#124840
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.