Closed
Bug 776233
Opened 12 years ago
Closed 11 years ago
[meta] sunspider regression in AWFY
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: smaug, Unassigned)
References
Details
(Whiteboard: [js:t])
there is some major regression in http://arewefastyet.com/
Comment 1•12 years ago
|
||
Is this the string-fasta thing?
Comment 2•12 years ago
|
||
http://arewefastyet.com/?a=b&view=breakdown says "dna", "format-tofte", "tagcloud", "unpack-code" all took a hit around the 20th.
tracking-firefox17:
--- → ?
Comment 3•12 years ago
|
||
See bug 775915 and bug 776200.
Comment 4•12 years ago
|
||
Tracking even though it's a meta bug because we don't necessarily know exactly the cause of all the regressions.
status-firefox17:
--- → affected
Summary: sunspider regression in AWFY → [meta] sunspider regression in AWFY
Whiteboard: [js:p1]
Comment 5•12 years ago
|
||
OK, I tracked down all the regressions. All but 3ms are fixed. The last 3ms is 777174. Keeping this open until it's all better but we'll just track bug 777174.
Depends on: 777174
Updated•12 years ago
|
Whiteboard: [js:p1] → [js:p1:fx17]
Comment 6•12 years ago
|
||
I think this has turned into a meta bug that doesn't need to be tracked in itself.
Whiteboard: [js:p1:fx17] → [js:t]
Comment 7•12 years ago
|
||
So this bug can be closed now, right?
Comment 8•12 years ago
|
||
Depends, does AWFY show that the regression is fixed? ;)
Comment 9•12 years ago
|
||
You're right. On July 19, JM on 64-bit (which is the one I care about, fwiw) was at 319-320. As of today, we are at 327. It's roughly the same on 32-bit. So, cannot consider this fixed.
Comment 10•11 years ago
|
||
Due to Ion landing, JM removal and BC landing, I think it's invalid now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•