Closed Bug 462939 Opened 16 years ago Closed 16 years ago

Slow test js1_6/extensions/regress-456826.js

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: dmandelin, Assigned: bc)

Details

Attachments

(1 file, 4 obsolete files)

This test is very slow; it takes 45+ minutes by itself on my MacBook. Should it be added to slow-n?
Assignee: general → bclary
Status: NEW → ASSIGNED
Flags: in-testsuite-
Flags: in-litmus-
Attached file slow-n-1.8.1.tests (obsolete) (deleted) —
Attached file slow-n-1.9.0.tests (obsolete) (deleted) —
Attached file slow-n-1.9.1.tests (obsolete) (deleted) —
David, try out the slow-n-1.9.1.tests for 1.9.1 mozilla-central/tracemonkey work. These show-n-*.tests include tests which require longer than 8 minutes for at least one combination of test type, build type etc. I would like to remove slow-n.tests and add slow-n-1.8.1.tests, slow-n-1.9.0.tests and slow-n-1.9.1.tests so that we can track "slowness" differently on each branch. Objections?
Attached patch patch (obsolete) (deleted) — Splinter Review
Attachment #346488 - Attachment is obsolete: true
Attachment #346489 - Attachment is obsolete: true
Attachment #346490 - Attachment is obsolete: true
Attachment #349416 - Flags: review?(dmandelin)
Whoops, don't know how I missed your previous comment. Anyway, sounds like a good idea. I tried the new patch with slow-n-1.9.1.tests with current TraceMonkey. (Are they intended to be used together?) I had to add 2 more slow tests: ecma_3/RegExp/regress-307456.js ecma_3/RegExp/regress-330684.js They seemed to be in the original slow-n but not in your new 1.9.1. I'm not sure if they were supposed to have been made not-slow or something. Please check into this and tell me if I'm doing something wrong or if they do need to be added to the list.
Attached patch patch v2 (deleted) — Splinter Review
Sorry, the previous patch missed tests that were slow on all branches. These should be better. They are intended to be branch specific. So, if you are testing mozilla-central or tracemonkey use slow-n-1.9.1.tests, etc. slow-n.tests is kind of old and hasn't had any review on if the old tests have become non-slow.
Attachment #349416 - Attachment is obsolete: true
Attachment #349467 - Flags: review?(dmandelin)
Attachment #349416 - Flags: review?(dmandelin)
Attachment #349467 - Flags: review?(dmandelin) → review+
Comment on attachment 349467 [details] [diff] [review] patch v2 This works for me. I just did a full run in 4m06s using slow-n-1.9.1.tests. I did get this line of output: -#- testcase 'js1_7/extensions/regress-458679.js' not found. I have seen such things before. I don't know exactly what conditions cause them but they don't seem harmful. (And it could be some sort of TM vs. M-C mismatch in this case.)
Checking in slow-n.tests; /cvsroot/mozilla/js/tests/slow-n.tests,v <-- slow-n.tests new revision: 1.11; previous revision: 1.10 done RCS file: /cvsroot/mozilla/js/tests/slow-n-1.8.1.tests,v done Checking in slow-n-1.8.1.tests; /cvsroot/mozilla/js/tests/slow-n-1.8.1.tests,v <-- slow-n-1.8.1.tests initial revision: 1.1 done RCS file: /cvsroot/mozilla/js/tests/slow-n-1.9.0.tests,v done Checking in slow-n-1.9.0.tests; /cvsroot/mozilla/js/tests/slow-n-1.9.0.tests,v <-- slow-n-1.9.0.tests initial revision: 1.1 done RCS file: /cvsroot/mozilla/js/tests/slow-n-1.9.1.tests,v done Checking in slow-n-1.9.1.tests; /cvsroot/mozilla/js/tests/slow-n-1.9.1.tests,v <-- slow-n-1.9.1.tests initial revision: 1.1 done
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: