Closed Bug 1060547 Opened 10 years ago Closed 9 years ago

2.57 linux32 dromaeo css regression on inbound (v.34) August 26 from revision 9d7eb12460ce

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: jmaher, Unassigned)

References

Details

(Keywords: perf, regression, Whiteboard: [talos_regression]) 

there is a noticeable drop in dromaeo css for linux32:
http://graphs.mozilla.org/graph.html#tests=[[72,131,33]]&sel=none&displayrange=7&datatype=running

I did some retriggers:
https://tbpl.mozilla.org/?tree=Mozilla-Inbound&fromchange=894b7372561d&tochange=4a3a302f1f31&jobname=Ubuntu%20HW%2012.04%20mozilla-inbound%20talos%20dromaeojs

and the lucky patch is from bug 1057219.  It is not all bad, if you look at the graph we bounced back, but we never backed out that patch.

I really want to document our regressions (purpose of this bug), and not back things out.  If we determine that the patch in bug 1057219 could be optimized we could probably realize a win!
Bug 1057219 is a minor incremental GC correctness fix and there's no way it legitimately caused a regression.
This has been shipped, I am going to mark this regression as wontfix.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.