Closed Bug 528654 Opened 12 years ago Closed 12 years ago
Intermittent timeout waiting for onload to fire in js1
_8 _1/trace/trace-test .js
the timeout occurred right after Josh's checkin http://hg.mozilla.org/mozilla-central/rev/88b83c564d3c which he backed out in http://hg.mozilla.org/mozilla-central/rev/0e01045dad63 I don't think this has occurred since, but I'll leave open for tracking for now. js1_8_1/trace/trace-test.js is too horking big though and should be split up.
While it did occur then, that was http://tinderbox.mozilla.org/showlog.cgi?log=Firefox-Unittest/1258109629.1258117678.13319.gz Linux mozilla-central debug test everythingelse on 2009/11/13 02:53:49 s: moz2-linux-slave11 and comment 0 is from a build six hours later. Plus, if a Linux build was affected by that changeset that touched nsLocalFileOSX.mm and a chunk of nsAppRunner.cpp inside an |#elif defined(XP_MACOSX)|, we've got way bigger problems than a jsreftest timeout :)
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox-Unittest/1258300816.1258308475.11657.gz Linux mozilla-central debug test everythingelse on 2009/11/15 08:00:16 s: moz2-linux-slave05 (Yeah yeah, that's another "run while something busted was in the tree" failure.)
I don't want to change js1_8_1/trace/trace-test.js since there are several open bugs on the existing js1_8_1/trace/trace-test.js which may depend on its large size. I think the appropriate solution will be to disable trace-test.js in the jsreftests and to create two additional tests by splitting the original.
Status: NEW → ASSIGNED
http://hg.mozilla.org/mozilla-central/rev/36022c7ab623 http://hg.mozilla.org/tracemonkey/rev/2ca2a236da89 I wrapped the exceptions in try catch blocks and removed the fails marker. Hopefully that will resolve the issue. marking fixed for now.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [orange] → [orange][fixed-in-tracemonkey]
Target Milestone: --- → mozilla1.9.3a1
Whiteboard: [orange][fixed-in-tracemonkey] → [fixed-in-tracemonkey]
You need to log in before you can comment on or make changes to this bug.