Closed
Bug 428330
Opened 17 years ago
Closed 17 years ago
browser-chrome tests timing out on moz2 unittest box
Categories
(Testing :: Mochitest, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rcampbell, Assigned: rcampbell)
References
Details
Attachments
(1 file)
|
484 bytes,
patch
|
Gavin
:
review+
|
Details | Diff | Splinter Review |
FAIL - Timed out - chrome://mochikit/content/browser/browser/base/content/test/browser_bug423833.js
FAIL - New tab should have page url, not about:neterror - Got http://www.mozilla.com/firefox/its-a-trap.html, expected http://127.0.0.1:55555/ - chrome://mochikit/content/browser/browser/base/content/test/browser_bug423833.js
FAIL - Timed out - chrome://mochikit/content/browser/browser/components/safebrowsing/content/test/browser_bug400731.js
|
Assignee | |
Comment 1•17 years ago
|
||
bumped the timeout constant to 30s per discussion in irc.
|
|
Assignee | |
Updated•17 years ago
|
Attachment #314872 -
Flags: review? → review?(gavin.sharp)
|
||
Updated•17 years ago
|
Attachment #314872 -
Flags: review?(gavin.sharp) → review+
|
||
Comment 2•17 years ago
|
||
I pushed this for Rob yesterday.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
|
|
||
Comment 3•17 years ago
|
||
I landed that patch on the trunk too, since we were seeing the same problem on the linux machine (the unit test machines automatically update runtests.pl, right?).
|
|
||
Comment 4•17 years ago
|
||
(In reply to comment #3)
> (the unit test machines automatically update runtests.pl, right?)
Er, nevermind that. The timeout isn't in runtests, it's in browser-test.js, and that is auto-updated.
|
|
Assignee | |
Comment 5•17 years ago
|
||
they autoupdate runtests.p[ly] too.
|
||
Updated•16 years ago
|
Component: Testing → BrowserTest
Product: Core → Testing
QA Contact: testing → browsertest
Version: Trunk → unspecified
|
||
Updated•7 years ago
|
Component: BrowserTest → Mochitest
You need to log in
before you can comment on or make changes to this bug.
Description
•