browser-chrome tests timing out on moz2 unittest box

RESOLVED FIXED

Status

Testing
Mochitest
RESOLVED FIXED
10 years ago
5 months ago

People

(Reporter: rc, Assigned: rc)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

10 years ago
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

10 years ago
Created attachment 314872 [details] [diff] [review]
browser test delay

bumped the timeout constant to 30s per discussion in irc.
Assignee: nobody → rcampbell
Status: NEW → ASSIGNED
Attachment #314872 - Flags: review?
(Assignee)

Updated

10 years ago
Attachment #314872 - Flags: review? → review?(gavin.sharp)
Attachment #314872 - Flags: review?(gavin.sharp) → review+

Comment 2

10 years ago
I pushed this for Rob yesterday.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
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?).
(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

10 years ago
they autoupdate runtests.p[ly] too.
Component: Testing → BrowserTest
Product: Core → Testing
QA Contact: testing → browsertest
Version: Trunk → unspecified
Component: BrowserTest → Mochitest
Product: Testing → Testing
You need to log in before you can comment on or make changes to this bug.