524731 - jsreftests - js1_5/Regress/regress-303213.js

Status: RESOLVED INCOMPLETE

(Core :: JavaScript Engine, defect)

Description

[Bob Clary [:bc] (inactive)]

jsreftests - js1_5/Regress/regress-303213.js is failing with no test results on the tracemonkey tinderbox for Windows.

Comment 1

[Bob Clary [:bc] (inactive)]

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.

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

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

Comment 3

[Bob Clary [:bc] (inactive)]

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

Comment 4

[Jesse Ruderman]

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.

Comment 5

[Matthew Gaudet (he/him) [:mgaudet]]

Bulk closing intermittents that haven't been updated since Sept 2024.

Comment 6

[Matthew Gaudet (he/him) [:mgaudet]]

Bulk closing intermittents that haven't been updated since Sept 2024.