Closed Bug 899611 Opened 11 years ago Closed 11 years ago

Intermittent TEST-UNEXPECTED-FAIL | jit-test\tests\jaeger\bug583158.js | --no-baseline --no-ion: jit-test\tests\jaeger\bug583158.js:6:0 ReferenceError: a is not defined

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 899697

People

(Reporter: RyanVM, Unassigned)

Details

(Keywords: intermittent-failure) 

https://tbpl.mozilla.org/php/getParsedLog.php?id=25885667&tree=Mozilla-Inbound

WINNT 5.2 mozilla-inbound leak test build on 2013-07-29 15:12:21 PDT for push c2dc8dbb77ef
slave: w64-ix-slave21

TEST-PASS | e:\builds\moz2_slave\m-in-w32-d-0000000000000000000\build\js\src\jit-test\tests\jaeger\bug583158.js | 
TEST-PASS | e:\builds\moz2_slave\m-in-w32-d-0000000000000000000\build\js\src\jit-test\tests\jaeger\bug583158.js | --ion-eager
TEST-PASS | e:\builds\moz2_slave\m-in-w32-d-0000000000000000000\build\js\src\jit-test\tests\jaeger\bug583158.js | --baseline-eager
TEST-PASS | e:\builds\moz2_slave\m-in-w32-d-0000000000000000000\build\js\src\jit-test\tests\jaeger\bug583158.js | --baseline-eager --no-ti --no-fpu
FAIL - e:\builds\moz2_slave\m-in-w32-d-0000000000000000000\build\js\src\jit-test\tests\jaeger\bug583158.js
TEST-UNEXPECTED-FAIL | e:\builds\moz2_slave\m-in-w32-d-0000000000000000000\build\js\src\jit-test\tests\jaeger\bug583158.js | --no-baseline --no-ion: e:\builds\moz2_slave\m-in-w32-d-0000000000000000000\build\js\src\jit-test\tests\jaeger\bug583158.js:6:0 ReferenceError: a is not defined

TEST-PASS | e:\builds\moz2_slave\m-in-w32-d-0000000000000000000\build\js\src\jit-test\tests\jaeger\bug583158.js | --no-baseline --no-ion --no-ti
Windows-only test harness wonkiness. The test is supposed to print that message. It's an expected exception. I don't know why the test is marked as failing.

Terrence, is this a dup?
I have no idea. The list of intermittent failures on windows bugs is too long to keep track of.

Perhaps we could switch to running jit-tests sequentially on windows for a week to see if multiprocessing is indeed the problem here?
Yes this was fixed by bug 899697.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.