Closed Bug 545323 Opened 14 years ago Closed 14 years ago

Intermittent timeout before test_browserGlue_distribution.js and after running test_browserGlue_corrupt_nobackup_default.js

Categories

(Firefox :: Bookmarks & History, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1265776802.1265778576.3124.gz
OS X 10.5.2 mozilla-central opt test xpcshell on 2010/02/09 20:40:02
s: moz2-darwin9-slave24

TEST-PASS | /builds/slave/mozilla-central-macosx-opt-unittest-xpcshell/build/xpcshell/tests/test_browser_places/unit/test_browserGlue_corrupt_nobackup_default.js | test passed

command timed out: 1200 seconds without output, killing pid 303
process killed by signal 9
program finished with exit code -1
elapsedTime=1238.395489
uh, this is new, and bad news, no idea how this can happen. The only relevant change in the last days is bug 457777 that looks innocent.
well no, there is also bug 538765.
Wups, forgot to update the bug after the second time it happened - it's probably just fallout from dolske's war on green, hanging when the iniparser failed. Looks like Standard8's followup in http://hg.mozilla.org/mozilla-central/rev/75beeb8eed5e fixed it enough to shift the failures elsewhere.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.