Closed
Bug 392596
Opened 17 years ago
Closed 17 years ago
spidermonkey-gc.tests is out of date
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: jorendorff, Unassigned)
Details
Attachments
(1 file)
It looks like almost all of the tests in that list have been renamed. I'm attaching a file that tries to follow the renamings... but in spidermonkey-gc.tests there were: js1_5/Array/regress-312278.js js1_5/Error/regress-312278.js whereas I was only able to find one file with that name in trunk: js1_5/extensions/regress-312278.js So the attached list is one line shorter than the one in trunk.
Attachment #277090 -
Flags: review?(bclary)
Comment 1•17 years ago
|
||
Comment on attachment 277090 [details]
updated list of spidermonkey GC tests
Thanks. Sorry I let this get out of sync.
js1_5/Array/regress-312278.js was the initial name for a security related test that didn't get checked in right away but that was finally check in under Error.
Attachment #277090 -
Flags: review?(bclary) → review+
Reporter | ||
Comment 2•17 years ago
|
||
bc, thanks for the review. I'm not a committer in CVS trunk. Do I need to get approval1.9+ or clear other hurdles? If not, would you please check this in?
Status: NEW → ASSIGNED
Comment 3•17 years ago
|
||
For the js tests, we don't need to worry about approvals but do need to respect tree closures. Checking in spidermonkey-gc.tests; /cvsroot/mozilla/js/tests/spidermonkey-gc.tests,v <-- spidermonkey-gc.tests new revision: 1.2; previous revision: 1.1 Thanks again.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•