Closed
Bug 1174108
Opened 9 years ago
Closed 9 years ago
web platform tests browser timeout is too short
Categories
(Testing :: web-platform-tests, defect)
Testing
web-platform-tests
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1173306
People
(Reporter: mak, Unassigned)
References
Details
In bug 959594 we just added a single pref to prefs_general.js, that was enough to cross the 30s timeout defined in testing/web-platform/harness/wptrunner/browsers/base.py init_timeout = 30 Looks like we are already very close to that time on some tinderboxes (Windows and OS X, linux was fine!), so maybe we should increase it? I did a try run with the same patches and a 60s timeout, and everything works correctly. https://treeherder.mozilla.org/#/jobs?repo=try&revision=d0a04c205b5f Unfortunately we need the fix in the tree ASAP, since the feature must ship in this iteration.
Flags: needinfo?(james)
Reporter | ||
Comment 1•9 years ago
|
||
Based on IRC discussion, bug 1173306 might have fixed the problem, indeed we had a multiline comment there. I'm going to make a new Try build now that this fix has made fx-team, and report what happens.
Depends on: 1173306
Flags: needinfo?(james)
Reporter | ||
Comment 2•9 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=8f58bdacfa0c
Reporter | ||
Comment 3•9 years ago
|
||
cool, looks like bug 1173306 did the trick! We were just unlucky to land minutes before it was merged to fx-team branch. Thank you for the help figuring this out
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•