test_printpreview.xhtml is a perma fail on windows 11 when testing with the October 2024 OS update
Categories
(Core :: Layout, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox135 | --- | fixed |
People
(Reporter: jmaher, Assigned: jmaher)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
We are working to update our CI from Windows11 Oct 2022 to Oct 2024. In doing this there are some failures. Specifically I would like to highlight from a debug log:
[task 2024-12-06T04:56:48.084Z] 04:56:48 INFO - TEST-UNEXPECTED-FAIL | layout/base/tests/chrome/test_printpreview.xhtml | Printing data:text/html,<!-- runTest41 --> and printpreview_bug1713404_ref.html should produce the same results - got false, expected true
I have a patch to skip this test, and wanted to file this bug so the layout team was aware of this and can investigate. We plan to migrate in 2-4 weeks, around the new year.
You can run this test on try by doing:
./mach try fuzzy -q 'test-windows11-64 mochitest-chrome' --worker-override='win11-64-2009=gecko-t/win11-64-24h2' --worker-override='win11-64-2009-gpu=gecko-t/win11-64-24h2-gpu' --worker-override='win11-64-2009-source=gecko-t/win11-64-24h2-source' --worker-override='win11-64-2009-ssd=gecko-t/win11-64-24h2-ssd' --worker-override='win11-64-2009-ssd-gpu=gecko-t/win11-64-24h2-ssd-gpu' --push-to-vcs layout/base/tests/chrome
Comment 1•2 months ago
|
||
That specific subtest seems expected to be fuzzy so seems it should just get updated to the right fuzz values rather than skipping all our print preview tests. Can you do that instead? The fuzz is printed out above the failure:
different: 256, maxDifference: 138
Assignee | ||
Comment 2•2 months ago
|
||
yes, this will work and I will submit a patch soon.
Assignee | ||
Comment 3•2 months ago
|
||
Updated•2 months ago
|
Comment 5•2 months ago
|
||
bugherder |
Description
•