Closed
Bug 653514
Opened 13 years ago
Closed 13 years ago
automatic package tests timed out on push to mozilla-central (then succeeded the second time)
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
1.1
People
(Reporter: myk, Assigned: myk)
Details
SDK package tests timed out on Windows 7 opt after a recent push to mozilla-central <http://tbpl.mozilla.org/?rev=c447a4e42b62>: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1304012632.1304013387.4169.gz&fulltext=1 However, on the exact same push and platform, they succeeded: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1304010215.1304010834.26484.gz&fulltext=1 Bizarre. Brian: any thoughts on what might be the problem here? At first glance of the logs, it isn't obvious.
Comment 1•13 years ago
|
||
wow, that first log is weird. It feels like the output of the test is getting rearranged kinda randomly: test-packaging appears to be run twice, and the second time appears in the middle of the test-api-utils output. This feels like some of the problems we had a few weeks ago with test output being buffered oddly, but I thought we fixed all that. It does kind of feel like there are two separate test processes, both writing to the same output file, interleaving with each other. Of the few dozen tests it ran in the main packages/* bunch before hanging, each one seems to appear exactly twice.
Assignee | ||
Updated•13 years ago
|
Priority: -- → P3
Target Milestone: --- → 1.0
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → myk
Assignee | ||
Comment 2•13 years ago
|
||
(automatic reprioritization of 1.0 bugs)
Priority: P3 → P2
Target Milestone: 1.0 → 1.1
Assignee | ||
Comment 3•13 years ago
|
||
I haven't seen this since, and it doesn't feel useful to keep the bug hanging around, and we've done some work on output buffering, so I'm going to resolve this bug, but please reopen if you see the problem again1
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•