Closed
Bug 678439
Opened 13 years ago
Closed 13 years ago
Linux debug SpiderMonkey --no-trace-jit builds have multiple "Assertion failure: sr.inMemory(), at ../../src/js/src/methodjit/RematInfo.h:83"
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: philor, Unassigned)
Details
Mac debug builds are fine (well, 10.5, 10.6 suffers from bug 678435), Windows debug isn't going yet because of bug 678213, but both Linux32 and Linux64 ¬t builds fail like http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Inbound/1313101688.1313103920.31783.gz TEST-UNEXPECTED-FAIL | jit_test.py -a -m | /builds/slave/m-in-lnx-dbg-spidermonkey-notracejit/src/js/src/jit-test/tests/arguments/bug508178.js: Assertion failure: sr.inMemory(), at ../../src/js/src/methodjit/RematInfo.h:83 TEST-UNEXPECTED-FAIL | jit_test.py -a -m -j | /builds/slave/m-in-lnx-dbg-spidermonkey-notracejit/src/js/src/jit-test/tests/arguments/bug508178.js: Assertion failure: sr.inMemory(), at ../../src/js/src/methodjit/RematInfo.h:83 TEST-UNEXPECTED-FAIL | jit_test.py -a -m -j -p | /builds/slave/m-in-lnx-dbg-spidermonkey-notracejit/src/js/src/jit-test/tests/arguments/bug508178.js: Assertion failure: sr.inMemory(), at ../../src/js/src/methodjit/RematInfo.h:83 TEST-UNEXPECTED-FAIL | jit_test.py -a -m | /builds/slave/m-in-lnx-dbg-spidermonkey-notracejit/src/js/src/jit-test/tests/arguments/bug554670-1.js: Assertion failure: sr.inMemory(), at ../../src/js/src/methodjit/RematInfo.h:83 TEST-UNEXPECTED-FAIL | jit_test.py -a -m -j | /builds/slave/m-in-lnx-dbg-spidermonkey-notracejit/src/js/src/jit-test/tests/arguments/bug554670-1.js: Assertion failure: sr.inMemory(), at ../../src/js/src/methodjit/RematInfo.h:83 TEST-UNEXPECTED-FAIL | jit_test.py -a -m -j -p | /builds/slave/m-in-lnx-dbg-spidermonkey-notracejit/src/js/src/jit-test/tests/arguments/bug554670-1.js: Assertion failure: sr.inMemory(), at ../../src/js/src/methodjit/RematInfo.h:83 etc. etc.
Reporter | ||
Comment 1•13 years ago
|
||
Windows debug is also fine, now that it's running.
Reporter | ||
Comment 2•13 years ago
|
||
And I certainly won't be digging back far enough to see who fixed it.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•