Closed Bug 450275 Opened 11 years ago Closed 11 years ago
_5/extensions/regress-434837-01 .js FAIL
.__count__ reason: Expected value '1', Actual value '3' .__count__ reason: Expected value '9', Actual value '3' .__count__ reason: Expected value '0', Actual value '3' x.test1 reason: Expected value 'true', Actual value 'false' x.test2 reason: Expected value 'false', Actual value 'true' x.test3 (1) reason: Expected value 'true', Actual value 'false' y.__count__ reason: Expected value '4', Actual value '3' tracemonkey: 20f1f3c72ae7 tip
occurs on mozilla-central now.
OS: Mac OS X → All
This is going to suck for the same reason that we suck at __proto__ lookup, as I discuss in bug 450274, comment 4. WONTFIX, too? sayrer: We can drop the priority on this one as well, likely.
Assignee: general → crowder
Priority: P1 → P3
Target Milestone: --- → mozilla1.9.1
WONTFIX and remove __count__ in mozilla2. /be
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
exclude it. /cvsroot/mozilla/js/tests/spidermonkey-n-1.9.1.tests,v <-- spidermonkey-n-1.9.1.tests new revision: 1.2; previous revision: 1.1 http://hg.mozilla.org/mozilla-central/rev/6ee837a12440
Status: RESOLVED → VERIFIED
js1_5/extensions/regress-434837-01.js should have been excluded for 1.9.1, 1.9.2. I mistakenly also excluded it for 1.9.0 as well. brendan, i excluded the entire test, but it appears that was overly aggressive. Are the failures of test1, test2, test3 above wontfix on 1.9.1 and later ?
All __count__ stuff is wontfix. Are the test failures covered by another bug? If not, please file. We want these tests split out. /be
test and exclusion lists modified in mc http://hg.mozilla.org/mozilla-central/rev/63ddf84277ae and cvs. filed Bug 474402
What needs documenting here?
There is no obvious need for documentation here, and no response to my request for details a month ago, so I'm removing the doc needed keyword.
You need to log in before you can comment on or make changes to this bug.