-
Notifications
You must be signed in to change notification settings - Fork 6k
[Impeller] Check coverage after screen clip #41129
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
jonahwilliams
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we need to CP this we'll need a test case
|
Working on a playground repro for this |
ac219dc to
f0602bb
Compare
|
Added a playground that hits this first frame: Before: |
jonahwilliams
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
Golden file changes have been found for this pull request. Click here to view and triage (e.g. because this is an intentional change). If you are still iterating on this change and are not ready to resolve the images on the Flutter Gold dashboard, consider marking this PR as a draft pull request above. You will still be able to view image results on the dashboard, commenting will be silenced, and the check will not try to resolve itself until marked ready for review. |
[Impeller] Check coverage after screen clip (cherry picked from commit 9b72a5d)
[Impeller] Check coverage after screen clip
…Pass (flutter#41178) This eliminates a lot of surface area when debugging non-recoverable frame failures such as flutter#41129. Every failure case should be covered with at least one log, but without recursive log spam.

Resolves flutter/flutter#124658.
Need to add error messages around all failed scenarios in EntityPass since we don't have a recovery and the whole frame fails to render. Will CP this.
Before: Failed rendering.
After: