Increase TIMEOUT_MULTIPLIER for CDP browser chrome tests for ASAN, TSAN and CCOV builds as well
Categories
(Remote Protocol :: CDP, defect, P1)
Tracking
(firefox111 fixed)
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
(Depends on 1 open bug)
Details
(Whiteboard: [webdriver:m6])
Attachments
(1 file)
Right now we only have the multiplier of 4
active for debug builds, but we should have at least the same value for ASAN and TSAN builds given that those are slow as well.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Actually also for CCOV jobs the timeout should be enhanced so that we cover all slowly running builds.
There are interesting results:
https://treeherder.mozilla.org/jobs?repo=try&revision=518affdcf6696701faa26ad716388a95729129af
While tsan seems to fail for browser_setCacheDisabled.js
(bug 1775791) all the CCOV tests perma fail in browser_lifecycleEvent.js
(bug 1734312). Most likely we will have to fix those dependencies first.
Assignee | ||
Comment 2•2 years ago
|
||
Depends on D166826
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
Ideally the Mochitest harness should provide a default multiplier per build type. I filed bug 1810395 for that. For now we should just go ahead and extend the timeout for the specific test as all the other tests are doing.
Comment 5•2 years ago
|
||
bugherder |
Description
•