Closed Bug 679599 Opened 14 years ago Closed 14 years ago

TI: Frequent "callStack.push is not a function item 1" errors in random jsreftests

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

For example, from the tip of JM http://tbpl.allizom.org/php/getParsedLog.php?id=5983278 Rev3 MacOSX Snow Leopard 10.6.2 jaegermonkey opt test jsreftest on 2011-08-15 22:38:32 PDT for push 74bfd74ca289 REFTEST TEST-START | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-420869-01.js FAILED! callStack.push is not a function REFTEST TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-420869-01.js | Unknown file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1 or from the tip of IM http://tbpl.allizom.org/php/getParsedLog.php?id=5996554 REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-420869-01.js | Unknown file:///home/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1 REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-422592.js | Unknown file:///home/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1 REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-424683-01.js | Unknown file:///home/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1 REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-426711.js | Unknown file:///home/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1 REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-427196-01.js | Unknown file:///home/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1 REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-427196-02.js | Unknown file:///home/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1 REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-427196-03.js | Unknown file:///home/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1 REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-429739.js | Unknown file:///home/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1 REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-434837-01.js | Unknown file:///home/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1 REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-435497-01.js | Unknown file:///home/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1 REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-435497-02.js | Unknown file:///home/cltbld/talos-slave/test/build/jsreftest/tests/shell.js:411: callStack.push is not a function item 1
I can't reproduce this, and have been pushing diagnostics to Try to figure out what is going on for this and bug 679247. This is a extremely slow process though. Is there a better way to do this? Something like triggering Mochitest-2 and jsreftests over and over until a failure occurs.
Ah, I noticed the little + and X buttons on the try builds, should be able to work faster using those.
Retriggering will work, but then you pay the price of downloading the build and tests and unpacking them every time. I don't think there's any elimination of duplicates in the reftest harness, so I'd expect that if you just add a patch to your stack that copies all of js/src/tests/jstests.list and pastes it back in 10 times, you'd get 10 runs for the price of one. Or, since the failures seem to be mostly if not exclusively in js1_5 tests, just change the .list to include only that one set 30 or 40 times.
Depends on: 680456
Or, maybe once you figure the cause out, it will just disappear without any visible reason.
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.