Closed Bug 614646 Opened 9 years ago Closed 7 years ago

[SeaMonkey 2.0 ?] Intermittent "Timed out while waiting for server startup." on mochitests, after 90 sec.

Categories

(Testing :: Mochitest, defect, minor)

1.9.1 Branch
x86
Windows Server 2003
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: sgautherie, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: intermittent-failure)

Bug 522617 comment 22:
{
Serge Gautherie (:sgautherie)      2010-11-23 02:47:51 PST

Let's open a new bug (to track releases) if this happens again.
}

***

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey2.0/1290595787.1290597252.11114.gz&fulltext=1
WINNT 5.2 comm-1.9.1 test mochitest-other on 2010/11/24 02:49:47
{
Timed out while waiting for server startup.
program finished with exit code 1
elapsedTime=165.703000
TinderboxPrint: mochitest-chrome<br/><em class="testfail">T-FAIL</em>
}

165.70 s >> 90 s.
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.