1886581 - Intermittent TEST-UNEXPECTED-TIMEOUT /css/css-page/page-name-001-print.html | single tracking bug

Status: RESOLVED INCOMPLETE

(Core :: Layout, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: ctuns [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=451534097&repo=mozilla-beta
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ZH-Psf1DRgmRXMGiU9eBdg/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/ZH-Psf1DRgmRXMGiU9eBdg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---

[task 2024-03-20T18:54:21.392Z] 18:54:21     INFO - TEST-START | /css/css-page/page-name-001-print.html
[task 2024-03-20T18:54:21.394Z] 18:54:21     INFO - PID 7412 | 1710960861392	Marionette	INFO	Testing http://web-platform.test:8000/css/css-page/page-name-001-print.html == http://web-platform.test:8000/css/css-page/page-name-001-ref.html
[task 2024-03-20T18:54:32.775Z] 18:54:32     INFO - TEST-UNEXPECTED-TIMEOUT | /css/css-page/page-name-001-print.html | expected FAIL
[task 2024-03-20T18:54:32.775Z] 18:54:32     INFO - TEST-INFO expected FAIL | took 11384ms
[task 2024-03-20T18:54:32.794Z] 18:54:32     INFO - PID 7412 | 1710960872800	Marionette	INFO	Stopped listening on port 57089
[task 2024-03-20T18:54:33.261Z] 18:54:33     INFO - Browser exited with return code 0
[task 2024-03-20T18:54:33.264Z] 18:54:33     INFO - Closing logging queue
[task 2024-03-20T18:54:33.264Z] 18:54:33     INFO - queue closed
[task 2024-03-20T18:54:33.324Z] 18:54:33     INFO - Application command: Z:\task_171095988250033\build\application\firefox\firefox.exe -marionette about:blank --wait-for-browser -profile C:\Users\task_171095988250033\AppData\Local\Temp\tmpkmlm3lnb
[task 2024-03-20T18:54:33.337Z] 18:54:33     INFO - PID 4680 | 1710960662852	Marionette	INFO	Marionette enabled
[task 2024-03-20T18:54:33.338Z] 18:54:33     INFO - PID 4680 | 1710960662918	Marionette	INFO	Listening on port 57106
[task 2024-03-20T18:54:33.338Z] 18:54:33     INFO - PID 4680 | [ERROR error_support::handling] suggest-unexpected: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base
[task 2024-03-20T18:54:33.339Z] 18:54:33     INFO - PID 4680 | console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base"
[task 2024-03-20T18:54:33.340Z] 18:54:33     INFO - Starting runner
[task 2024-03-20T18:54:34.453Z] 18:54:34     INFO - TEST-START | /css/css-page/page-name-abspos-001-print.html

Comment 1

[Daniel Holbert [:dholbert]]

Some notes:

• The test here is here, and I added it a few months ago in bug 1875186 to get code-coverage for a known bug.

• The test doesn't do anything dynamic or fancy (other that testing printing), and this wasn't a failure on a slow platform (this was Windows 11 x64 22H2 WebRender DevEdition opt Web platform tests test-windows11-64-2009-devedition-qr/opt-web-platform-tests-print-reftest Wp -- not code-coverage or debug or TSAN/ASAN for example, where tests can take a while). So it's not obvious why this test in particular would timeout here.

• But actually, it looks like ~every nearby test is running dangerously close to the timeout threshold (and in some cases, some nearby tests are timing out and are annotated as expected-timeout). Scrolling up in the log, it looks like the previous few tests before this were taking 5-7 seconds each, and we have e.g. TEST-KNOWN-INTERMITTENT-TIMEOUT | /css/css-page/monolithic-overflow-024-print.html | took 10028ms a bit further up.

Maybe we should use a more permissive timeout threshold for our print WPT tests? It seems like maybe there's some overhead involved here that we need to tolerate. Or maybe we need to investigate what's causing that overhead.

Comment 2

[Daniel Holbert [:dholbert]]

(In reply to Daniel Holbert [:dholbert] from comment #1)

• But actually, it looks like ~every nearby test is running dangerously close to the timeout threshold

I filed bug 1886588 with some more notes on this.

Comment 3

[Intermittent Failures Robot]

1 failures in 3791 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-beta: 1

Platform and build breakdown:

• windows11-64-2009-devedition-qr: 1
  • opt: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1886581&startday=2024-03-18&endday=2024-03-24&tree=all

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.