Open Bug 1936464 Opened 1 year ago Updated 1 year ago

browser_test_group_fission.js almost perma fail on new windows 11 Oct 2024 update in CI

Categories

(Core :: Panning and Zooming, defect, P3)

defect

Tracking

()

People

(Reporter: jmaher, Unassigned)

References

(Blocks 1 open bug)

Details

I am running tests in ci on the new windows 11 update, and there are some failures.

some errors from a debug log:

[task 2024-12-06T21:46:02.418Z] 21:46:02     INFO - TEST-PASS | gfx/layers/apz/test/mochitest/browser_test_group_fission.js | http://mochi.test:8888/browser/gfx/layers/apz/test/mochitest/helper_fission_force_empty_hit_region.html | center of regular iframe should hit iframe doc hit info - 
[task 2024-12-06T21:46:02.419Z] 21:46:02     INFO - TEST-PASS | gfx/layers/apz/test/mochitest/browser_test_group_fission.js | http://mochi.test:8888/browser/gfx/layers/apz/test/mochitest/helper_fission_force_empty_hit_region.html | center of regular iframe should hit iframe doc scrollid - 
[task 2024-12-06T21:46:02.421Z] 21:46:02     INFO - TEST-PASS | gfx/layers/apz/test/mochitest/browser_test_group_fission.js | http://mochi.test:8888/browser/gfx/layers/apz/test/mochitest/helper_fission_force_empty_hit_region.html | center of regular iframe should hit iframe doc layersid - 
[task 2024-12-06T21:46:02.421Z] 21:46:02     INFO - Buffered messages logged at 21:33:55
[task 2024-12-06T21:46:02.423Z] 21:46:02     INFO - Console message: [JavaScript Warning: "Partitioned cookie or storage access was provided to https://example.com/browser/gfx/layers/apz/test/mochitest/helper_fission_empty.html because it is loaded in the third-party context and dynamic state partitioning is enabled."]
[task 2024-12-06T21:46:02.423Z] 21:46:02     INFO - Buffered messages logged at 21:33:56
[task 2024-12-06T21:46:02.425Z] 21:46:02     INFO - Console message: [JavaScript Warning: "Partitioned cookie or storage access was provided to https://example.org/browser/gfx/layers/apz/test/mochitest/helper_fission_empty.html because it is loaded in the third-party context and dynamic state partitioning is enabled."]
[task 2024-12-06T21:46:02.425Z] 21:46:02     INFO - Buffered messages logged at 21:35:21
[task 2024-12-06T21:46:02.426Z] 21:46:02     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 7
[task 2024-12-06T21:46:02.429Z] 21:46:02     INFO - Buffered messages logged at 21:37:01
[task 2024-12-06T21:46:02.429Z] 21:46:02     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 6
[task 2024-12-06T21:46:02.429Z] 21:46:02     INFO - Buffered messages logged at 21:38:31
[task 2024-12-06T21:46:02.430Z] 21:46:02     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 5
[task 2024-12-06T21:46:02.430Z] 21:46:02     INFO - Buffered messages logged at 21:40:01
[task 2024-12-06T21:46:02.431Z] 21:46:02     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 4
[task 2024-12-06T21:46:02.433Z] 21:46:02     INFO - Buffered messages logged at 21:41:31
[task 2024-12-06T21:46:02.434Z] 21:46:02     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 3
[task 2024-12-06T21:46:02.436Z] 21:46:02     INFO - Buffered messages logged at 21:43:01
[task 2024-12-06T21:46:02.436Z] 21:46:02     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 2
[task 2024-12-06T21:46:02.437Z] 21:46:02     INFO - Buffered messages logged at 21:44:31
[task 2024-12-06T21:46:02.438Z] 21:46:02     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 1
[task 2024-12-06T21:46:02.438Z] 21:46:02     INFO - Buffered messages finished
[task 2024-12-06T21:46:02.439Z] 21:46:02     INFO - TEST-UNEXPECTED-FAIL | gfx/layers/apz/test/mochitest/browser_test_group_fission.js | Test timed out - 

you can see this happens frequently enough and my script to "green up" added an annotation for this test. I have a patch to disable this on the new windows version here, and we plan to deploy that in 2-4 weeks, when most changes have been checked in.

this bug is fined as a work item for the panning and zooming team to investigate this when time permits.

If you want to investigate this and run on try server, here is a command to use:
./mach try fuzzy -q 'test-windows11-64 browser-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 gfx/layers/apz/test/mochitest

This test is going to be removed soon as its contents are being ported to mochitest-plain in bug 1841896.

The severity field is not set for this bug.
:botond, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(botond)

Marking as S4 per comment 1.

Severity: -- → S4
Flags: needinfo?(botond)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.