Land a reftest for bug 1552923
Categories
(Core :: Graphics: WebRender, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox106 | --- | fixed |
People
(Reporter: hiro, Assigned: hiro)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
2.61 KB,
patch
|
Details | Diff | Splinter Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
I wrote a reftest bug 1552923, but apparently it needs bug 1646629 (a change to make reftest-no-flush work properly), so I am going to defer adding the reftest into this bug.
Assignee | ||
Comment 2•2 years ago
|
||
Yes, coincidently Boris is now touching some relevant stuff in bug 1776077.
I will try to see if this reftest now works or not since bug 1646629 landed.
Assignee | ||
Comment 3•2 years ago
|
||
Comment 5•2 years ago
|
||
Backed out for causing reftest failures on replace-with-new-positive-delay-animation.html
- Backout link
- Push with failures
- Failure Log
- Failure line: REFTEST TEST-UNEXPECTED-FAIL | layout/reftests/css-animations/replace-with-new-positive-delay-animation.html == layout/reftests/css-animations/replace-with-new-positive-delay-animation-ref.html | image comparison, max difference: 255, number of differing pixels: 10000
- Analyzer link: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/U8FI2OTATaWg2raUE4niTQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
Assignee | ||
Comment 6•2 years ago
|
||
Hmm, it failed on Android. And I suppose just waiting for two frames isn't sufficient for Android. :/
Assignee | ||
Comment 7•2 years ago
|
||
I am going to skip the reftest on Android. On Android even with waiting for 1s the test fails, the green box doesn't appear, it should be triggered by setting the second animation. When I open the reftest in question with some tweak (using window.onload instead of MozReftestInvalidate) on GeckoView example, the green box appears properly. So I suppose it's an issue in our reftest harness (Android specific, it's weird though) rather than a real issue.
Assignee | ||
Comment 8•2 years ago
|
||
Filed bug 1787682 for the Android failure.
Comment 10•2 years ago
|
||
bugherder |
Description
•