Closed Bug 397545 Opened 18 years ago Closed 18 years ago

jsDriver.pl claims e4x/Regress/regress-380833.js fails

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: jorendorff, Assigned: bc)

References

()

Details

Attachments

(2 files)

Attached file test output
When I run the tests with jsDriver.pl, this one fails: http://lxr.mozilla.org/mozilla/source/js/tests/e4x/Regress/regress-380833.js But when I cat together the relevant shell.js files and run it manually, the last line of output is: PASSED! Section 1 of test - Crash during GC after uneval I think the test is actually passing and jsDriver.pl is incorrectly logging it as a failure, maybe because the output (see attachment) contains the string FAILED.
Yep, it happens when you don't specify -R as an option due to # watch for failures if ($line =~ /failed!/i) { $failure_lines .= $line; } in execute_tests. Personally, I would just like to make the default -R and forget the old behavior of just looking for FAILED! I'm open to suggestions.
Attached file patch v1
See if this works for you.
Attachment #282391 - Flags: review?(jorendorff)
Comment on attachment 282391 [details] patch v1 Works for me.
Attachment #282391 - Flags: review?(jorendorff) → review+
Assignee: general → bclary
/cvsroot/mozilla/js/tests/jsDriver.pl,v <-- jsDriver.pl new revision: 1.71; previous revision: 1.70
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Flags: in-testsuite-
Flags: in-litmus-
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: