Intermittent devtools/client/responsive.html/test/browser/browser_toolbox_swap_browsers.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. -

RESOLVED FIXED in Firefox 52

Status

defect
P1
normal
RESOLVED FIXED
3 years ago
Last year

People

(Reporter: intermittent-bug-filer, Assigned: jryans)

Tracking

({intermittent-failure})

unspecified
Firefox 53
Dependency tree / graph
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(firefox51 unaffected, firefox52 fixed, firefox53 fixed)

Details

Assignee

Updated

3 years ago
Priority: -- → P3
Comment hidden (Intermittent Failures Robot)
Comment hidden (Intermittent Failures Robot)
Comment hidden (Intermittent Failures Robot)
Comment hidden (Intermittent Failures Robot)
Comment hidden (Intermittent Failures Robot)
Comment hidden (Intermittent Failures Robot)
Comment hidden (Intermittent Failures Robot)
Comment hidden (Intermittent Failures Robot)
Comment hidden (Intermittent Failures Robot)
Practically all failures are on linux64-asan, e10s.

This e10s-only test runs in < 10 seconds on linux64 opt/pgo but typically takes > 40 seconds on linux64-asan. At 45 seconds, it times out.
It feels like requestLongerTimeout() would be appropriate for this test on asan...but not so much for other platforms. Looking for suggestions for how to deal with this, and similar cases of run-too-long-on-platform (maybe bug 1292233).

Some possible approaches:
 - requestLongerTimeout()
 - skip-if = asan # runs for too long on asan
 - requestLongerTimeout() for this test, on asan only, somehow
 - increase default timeout on asan for all mochitests, somehow
Flags: needinfo?(ryanvm)
Flags: needinfo?(jmaher)
I like the list of approaches here- I would question if running this test on ASAN brings value and if it isn't important we could do less ASAN testing :)

Assuming it is important to run this test on ASAN, I think option 3 or 4.  The simplest thing would be #4, but that would be harder to debug/understand what is going on- which leads me to #3.  How do we do that, I assume we could/should pass in mozinfo data to the browser and requestLogerTimeout could have the data from mozinfo :)
Flags: needinfo?(jmaher)
See Also: → 1292233
Assignee

Comment 13

3 years ago
As with bug 1292233, I don't think this test itself can be made much faster...  I would be okay with any of the approaches in comment 11.
Depends on: 1313187
I'm proceeding with a variation on the last option in Comment 11, increasing the default timeout on asan for all 'browser' flavored mochitests, from 45 to 90 seconds - bug 1313187. If that works, I'll dup this bug to that one.
Assignee: nobody → gbrown
Flags: needinfo?(ryanvm)
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1313187
Comment hidden (Intermittent Failures Robot)
Comment hidden (Intermittent Failures Robot)
Bug 1313187 resolved all the Linux64-asan instances (the majority), as expected. But the test also runs too long on win32-debug occasionally.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Duplicate of this bug: 1316893
Assignee

Updated

3 years ago
Flags: needinfo?(jryans)
Comment hidden (Intermittent Failures Robot)
Assignee

Comment 21

3 years ago
Let's requestLongerTimeout to fix the rest.
Assignee: gbrown → jryans
Status: REOPENED → ASSIGNED
Flags: needinfo?(jryans)
Priority: P3 → P1

Comment 22

3 years ago
Pushed by jryans@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/66a58018adea
Longer timeout for browser_toolbox_swap_browsers.js. r=me

Comment 23

3 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/66a58018adea
Status: ASSIGNED → RESOLVED
Closed: 3 years ago3 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 53
Comment hidden (Intermittent Failures Robot)

Updated

Last year
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.