Bug 1886581 clued me into the fact that we've got some suspicious delays in our WPT logs for print tests, at least in the log linked there. Log (for an opt build with no obvious reason to be slow): https://treeherder.mozilla.org/logviewer?job_id=451534097&repo=mozilla-beta&lineNumber=2669 Here's a snippet of that log, showing just a few pairs of consecutive lines where there's this supsicious delay in the timestamps between them (which is responsible for essentially the entire test duration): ``` 18:45:50 INFO - PID 7124 | 1710960350188 Marionette INFO Testing http://web-platform.test:8000/css/CSS2/pagination/block-page-break-inside-avoid-15-print.html == http://web-platform.test:8000/css/CSS2/pagination/block-page-break-inside-avoid-15-print-ref.html 18:45:57 INFO - PID 7124 | 1710960357253 Marionette INFO Rendering page 1/5 [note, 7-second delay there] 18:47:45 INFO - PID 7124 | 1710960465719 Marionette INFO Testing http://web-platform.test:8000/css/CSS2/pagination/table-page-break-inside-avoid-5-print.html == http://web-platform.test:8000/css/CSS2/pagination/table-page-break-inside-avoid-5-print-ref.html 18:47:51 INFO - PID 7124 | 1710960471470 Marionette INFO Rendering page 1/4 [note, 6-second delay there] ``` We should see about either fixing these delays; or if they're not-easily-avoidable, we should increase the timeout threshold for these tests so that the delays don't cause spurious reports of intermittent test-timeouts.
Bug 1886588 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Bug 1886581 clued me into the fact that we've got some suspicious delays in our WPT logs for print tests, at least in the log linked there. Log (for an opt build with no obvious reason to be slow): https://treeherder.mozilla.org/logviewer?job_id=451534097&repo=mozilla-beta&lineNumber=2669 Here's a snippet of that log, showing just a few pairs of consecutive lines where there's this supsicious delay in the timestamps between them (which is responsible for essentially the entire test duration): ``` 18:45:50 INFO - PID 7124 | 1710960350188 Marionette INFO Testing http://web-platform.test:8000/css/CSS2/pagination/block-page-break-inside-avoid-15-print.html == http://web-platform.test:8000/css/CSS2/pagination/block-page-break-inside-avoid-15-print-ref.html 18:45:57 INFO - PID 7124 | 1710960357253 Marionette INFO Rendering page 1/5 [note, 7-second delay there] 18:47:45 INFO - PID 7124 | 1710960465719 Marionette INFO Testing http://web-platform.test:8000/css/CSS2/pagination/table-page-break-inside-avoid-5-print.html == http://web-platform.test:8000/css/CSS2/pagination/table-page-break-inside-avoid-5-print-ref.html 18:47:51 INFO - PID 7124 | 1710960471470 Marionette INFO Rendering page 1/4 [note, 6-second delay there] ``` We should see about either fixing these delays; or if they're not-easily-avoidable, we should increase the timeout threshold for this category of tests (to be substantially larger than the current 10s threshold), so that the delays don't cause spurious reports of intermittent test-timeouts.