Intermittent layout/reftests/bugs/1878294-1.html == layout/reftests/bugs/1878294-1-ref.html | single tracking bug
Categories
(Core :: Graphics: WebRender, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox123 | --- | unaffected |
firefox124 | --- | unaffected |
firefox125 | --- | wontfix |
People
(Reporter: intermittent-bug-filer, Assigned: tnikkel)
References
(Regression)
Details
(Keywords: intermittent-failure, regression, test-verify-fail)
Attachments
(1 file)
Filed by: smolnar [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=448780678&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/XeO6zDXCQKKjaO1LDzqIlQ/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/XeO6zDXCQKKjaO1LDzqIlQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
REFTEST TEST-LOAD | file:///builds/worker/workspace/build/tests/reftest/tests/layout/reftests/bugs/1878294-1.html | 0 / 1 (0%)
[task 2024-02-28T14:09:53.292Z] 14:09:53 INFO - [Parent 5277, Main Thread] WARNING: WebProgress Ignored: no longer current window global: file /builds/worker/checkouts/gecko/dom/ipc/BrowserParent.cpp:3131
[task 2024-02-28T14:09:53.328Z] 14:09:53 INFO - ### XPCOM_MEM_BLOAT_LOG defined -- logging bloat/leaks to /tmp/tmp8yti_55y.mozrunner/runreftest_leaks_tab_pid5526.log
[task 2024-02-28T14:09:53.366Z] 14:09:53 INFO - [Child 5526, Main Thread] WARNING: could not set real-time limit in CubebUtils::InitLibrary: file /builds/worker/checkouts/gecko/dom/media/CubebUtils.cpp:693
[task 2024-02-28T14:09:53.459Z] 14:09:53 INFO - [Child 5526, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80520012 (NS_ERROR_FILE_NOT_FOUND): file /builds/worker/checkouts/gecko/layout/style/Loader.cpp:2103
[task 2024-02-28T14:09:53.729Z] 14:09:53 INFO - REFTEST INFO | drawWindow flags = DRAWWINDOW_DRAW_CARET | DRAWWINDOW_DRAW_VIEW | DRAWWINDOW_USE_WIDGET_LAYERS; window size = 800,1000; test browser size = 800,1000
[task 2024-02-28T14:09:54.299Z] 14:09:54 INFO - ### XPCOM_MEM_BLOAT_LOG defined -- logging bloat/leaks to /tmp/tmp8yti_55y.mozrunner/runreftest_leaks_tab_pid5553.log
[task 2024-02-28T14:09:54.344Z] 14:09:54 INFO - [Child 5553, Main Thread] WARNING: could not set real-time limit in CubebUtils::InitLibrary: file /builds/worker/checkouts/gecko/dom/media/CubebUtils.cpp:693
[task 2024-02-28T14:10:11.014Z] 14:10:11 INFO - 1709129411011 addons.xpi ERROR System addon update list error Error: Failed downloading XML, status: 0, channelStatus: 2152398861, errorCode: 2, reason: error
[task 2024-02-28T14:14:53.665Z] 14:14:53 INFO - REFTEST TEST-UNEXPECTED-FAIL | layout/reftests/bugs/1878294-1.html == layout/reftests/bugs/1878294-1-ref.html | load failed: timed out waiting for pending paint count to reach zero (waiting for updateCanvasPending)
[task 2024-02-28T14:14:53.671Z] 14:14:53 INFO - REFTEST INFO | Saved log: START file:///builds/worker/workspace/build/tests/reftest/tests/layout/reftests/bugs/1878294-1.html
[task 2024-02-28T14:14:53.674Z] 14:14:53 INFO - REFTEST INFO | Saved log: [CONTENT] Using browser remote=true
Comment 1•1 year ago
|
||
:tnikkel, since you are the author of the regressor, bug 1878294, could you take a look?
For more information, please visit BugBot documentation.
Comment 2•1 year ago
|
||
Set release status flags based on info from the regressing bug 1878294
Assignee | ||
Comment 3•1 year ago
|
||
This is expected to some degree. When writing tests that tweak a property in order to maintain an active entry in the layer activity tracker some platforms don't have enough time to paint and trigger the reftest finishing conditions before the next tweak. I've written several tests that use this same strategy for testing this kind of bug. I've skipped the test on the slower platforms (linux asan, linux tsan, android debug) to minimize this, but it's likely going to be hit at an intermittent rate. That's about the best I've been able to do while still testing the original bug.
I don't think we need to track this on a release basis, so I've set the release tracking flags to try to minimize bugmail/release tracker triage time, but I'm not sure what's the best way to do that.
Comment 4•1 year ago
|
||
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 5•1 year ago
|
||
I checked that this still reliably reproduces the original bug with the original patch backed out.
Updated•1 year ago
|
Comment hidden (Intermittent Failures Robot) |
Comment 8•1 year ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Description
•