428330 - browser-chrome tests timing out on moz2 unittest box

Status: RESOLVED FIXED

(Testing :: Mochitest, defect)

Description

[Rob Campbell [:rc] (:robcee)]

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

Comment 1

[Rob Campbell [:rc] (:robcee)]

Attachment: browser test delay

bumped the timeout constant to 30s per discussion in irc.

Comment 2

[Benjamin Smedberg]

I pushed this for Rob yesterday.

Comment 3

[:Gavin Sharp [email: [e-mail]]]

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

[:Gavin Sharp [email: [e-mail]]]

(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.

Comment 5

[Rob Campbell [:rc] (:robcee)]

they autoupdate runtests.p[ly] too.