Use a different delay for navigation timers on slow platforms (debug/asan/...)
Categories
(Remote Protocol :: Agent, task, P1)
Tracking
(firefox104 fixed)
Tracking | Status | |
---|---|---|
firefox104 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
Details
(Whiteboard: [webdriver:m4][webdriver:external])
Attachments
(1 file)
See investigation at Bug 1766708 comment #2, on some platforms the unload timer for the shared waitForNavigationCompleted timer is too low to detect an actual expected navigation.
We should increase the delay used for those timers on slow platforms.
Default timer is set at https://searchfox.org/mozilla-central/rev/a730b83206183bf097820c5780eef0d5e4103b9d/remote/shared/Navigate.jsm#119
We can read debug & asan flags from AppConstants.jsm https://searchfox.org/mozilla-central/rev/a730b83206183bf097820c5780eef0d5e4103b9d/toolkit/modules/AppConstants.jsm#243-255
Suggested by :whimboo on Bug 1766708: "Maybe when doing that we might consider a separate Constants.jsm module for Remote Agent?"
Assignee | ||
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Maybe we should not just add longer times for ASAN or debug builds but similarly to web-platform tests work with a multiplier. That way we can apply the same behavior to other timeouts as well as long as we are flexible and there is no strict constrain with a specification.
Updated•3 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Hi Julian. Adding this to M4. Add the point value when you are ready.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 4•2 years ago
|
||
Alternatively we can disable the perma on ccov
Comment 6•2 years ago
|
||
bugherder |
Description
•