Intermittent /css/css-contain/content-visibility/content-visibility-resize-observer-no-error.html | single tracking bug
Categories
(Core :: Layout, defect, P5)
Tracking
()
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: intermittent-failure, intermittent-testcase)
Filed by: dholbert [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=426306026&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Ny-0CHoHQXWLLddOgMJHBQ/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: 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/Ny-0CHoHQXWLLddOgMJHBQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
I ran into this on a try run, which had zero changes to Gecko itself and zero changes to this particular test. Treeherder doesn't have any suggested matches, so I'm assuming this is a latent intermittent failure that I just got lucky enough to be the first one to notice.
Comment 1•2 years ago
|
||
In the reftest failure analyzer, the screenshot of the testcase shows a 400px tall blue area, while the screenshot of the reference case shows a 100px tall blue area.
Comment 2•2 years ago
•
|
||
I can briefly see the 400px-tall-blue-area rendering, when I load (or shift+reload) the test directly, e.g. at http://wpt.live/css/css-contain/content-visibility/content-visibility-resize-observer-no-error.html
(Really, the 400px tall area is two 200px-divs.)
It looks like we're doing an initial paint of the page with the contain-intrinsic-size
-granted heights on these divs, which we perhaps should not be doing...? That's what's creating an opportunity for the reftest snapshot to capture this initial unexpectedly-tall rendering.
Comment hidden (Intermittent Failures Robot) |
Comment 4•1 year ago
|
||
I have tried with the command from bug 1865267 comment 12 and cannot reproduce.
We don't have any annotation in content-visibility-resize-observer-no-error.html.ini and it looks the last report was on 2023-08-17 for linux1804-64-qr opt
. It's possible this has been fixed by recent changes.
(In reply to Treeherder Bug Filer from comment #0)
I ran into this on a try run, which had zero changes to Gecko itself and zero changes to this particular test. Treeherder doesn't have any suggested matches, so I'm assuming this is a latent intermittent failure that I just got lucky enough to be the first one to notice.
@Daniel: Are you still able to reproduce? Otherwise, I guess we can close?
Comment 5•1 year ago
|
||
Comment 0 was just a one-off on Try; I'm not sure how reproducible that would be. Apparently not very reproducible since we only ever got that one report of an actual test-failure, it seems.
But the thing I described in comment 2 (flicker of taller blue content at page-load): I can still reproduce that in older builds, but it's gone away in newer builds. Fix range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9ea04a2cc829da8ce1048f38bb015b869d9273aa&tochange=95679f6ce2544b21ec9cfd0d19961058d60155d6
--> Looks like we can consider this a duplicate of bug 1807253. Thanks!
Description
•