REFTEST TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-jsreftest/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-336410-2.js | No test results reported. (SCRIPT

RESOLVED FIXED

Status

()

RESOLVED FIXED
8 years ago
6 years ago

People

(Reporter: bas.schouten, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
Windows Server 2003
intermittent-failure
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1282107392.1282110996.13171.gz#err0
WINNT 5.2 mozilla-central debug test jsreftest on 2010/08/17 21:56:32
s: win32-slave31


REFTEST TEST-START | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-jsreftest/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-336410-2.js
++DOMWINDOW == 8 (058D10F8) [serial = 3215] [outer = 0553D058]
BUGNUMBER: 336410
STATUS: Integer overflow in array_toSource
--- NOTE: IN THIS TESTCASE, WE EXPECT EXIT CODE 0 ---
--- NOTE: IN THIS TESTCASE, WE EXPECT EXIT CODE 5 ---
STATUS: Creating 128M length string
--DOMWINDOW == 7 (09A8EEB8) [serial = 3214] [outer = 0553D058] [url = data:text/html,%3C%21%2D%2DCLEAR%2D%2D%3E]
--DOMWINDOW == 6 (05892B98) [serial = 3213] [outer = 0553D058] [url = file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-jsreftest/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-336409-2.js]
REFTEST TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-jsreftest/build/jsreftest/tests/jsreftest.html?test=js1_5/extensions/regress-336410-2.js | No test results reported. (SCRIPT)

Updated

8 years ago
Duplicate of this bug: 588311

Comment 2

8 years ago
This test is already disabled for the browser on 64bit builds.

The error is not a time out but a failure of the test to run the reportCompare function which sets up the array of test results that reftest uses to report the test results. It can be caused by a) not calling reportCompare or its related functions or b) some other situation where the script fails to execute properly or perhaps terminates silently due to an unknown error.

If there has not been a change in the test and there has not been a change in the test environment, then a sudden appearance of this error is troublesome and an indication that something has regressed.

We can disable this test for the browser if necessary, but the knee jerk reaction should be resisted until we know there has not been a problem introduced into the code.
Blocks: 438871
OS: Windows 7 → Windows Server 2003
Whiteboard: [orange]
Version: unspecified → Trunk
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)

Comment 10

8 years ago
I have a patch to disable this test for Windows. I'll attach as soon as I complete testing it.
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)

Comment 22

8 years ago
Created attachment 468066 [details] [diff] [review]
patch

This will disable the test on Windows as well as 64 bit.
Attachment #468066 - Flags: review?(brendan)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Attachment #468066 - Flags: review?(brendan) → review+
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)

Comment 34

8 years ago
test disabled for windows on tracemonkey.
http://hg.mozilla.org/tracemonkey/rev/7e5cdd50de10

mozilla-central looks like a florida university football game, so I'll hold of pushing there until it clears up.
See comment 30 - I already pushed it to mozilla-central (Saturday is a nice calm day, apparently everybody watches college football all day, and then attacks the tree while waiting for NFL to start on Sunday).

Comment 36

8 years ago
Ok. Thanks Philor.

Unless the total memory changed on the test machines, something changed in the code to make the oom cause the test not to report the result in the gTestcases array. It is probably not a big deal, and this bug can be marked wontfix or invalid, but I'd like someone who knows what has been happening in the js memory land to make that call.
Comment hidden (Treeherder Robot)

Comment 38

8 years ago
http://hg.mozilla.org/mozilla-central/rev/7e5cdd50de10
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Keywords: intermittent-failure
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.