jsreftests - js1_5/Regress/regress-303213.js is failing with no test results on the tracemonkey tinderbox for Windows.
http://hg.mozilla.org/tracemonkey/rev/53fca7890848 skip test for opt as well as debug windows. this does not occur in my local vm. It may be related to the amount of memory in the unittest machine. locally I have 2G.
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox-Unittest/1260563659.1260567912.28270.gz Linux mozilla-central opt test everythingelse on 2009/12/11 12:34:19 s: moz2-linux-slave19 REFTEST TEST-UNEXPECTED-FAIL | file:///builds/moz2_slave/mozilla-central-linux-opt-unittest-everythingelse/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-303213.js | timed out waiting for onload to fire
http://hg.mozilla.org/tracemonkey/rev/deb1a7099116 http://hg.mozilla.org/mozilla-central/rev/19c480485f4f skip js1_5/Regress/regress-303213.js due to random timeouts
Assignee: general → bclary
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
When you disable a randomly-orange test, please either: * Annotate the manifest with a reference to an OPEN bug, which could be the [orange] bug turned into an [orange][test disabled] bug, OR * Annotate the manifest with an explanation, e.g. "We don't run OOM tests in xpcshell because...", OR * Mark the test as "slow" so it is automatically protected from running with short timeouts. This helps maintain the sanity-preserving invariant that test manifests do not refer to bugs that are marked as fixed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [orange][fixed-in-tracemonkey] → [orange][test disabled]
Whiteboard: [orange][test disabled] → [test disabled]
You need to log in before you can comment on or make changes to this bug.