Closed
Bug 1103127
Opened 11 years ago
Closed 11 years ago
51% Linux* TART|TSVGX regression on Mozilla-Beta (v.34) Nov 20th from push 0bcee2fc8e0b
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jmaher, Unassigned)
References
Details
(Keywords: perf, regression, Whiteboard: [talos_regression][dzalerts])
Attachments
(1 file)
|
1.61 KB,
patch
|
Gavin
:
review+
Gavin
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
Here is a graph server outline showing the regression;
http://graphs.mozilla.org/graph.html#tests=%5B%5B293,53,33%5D,%5B293,53,35%5D%5D&sel=1415996995821,1416601795821&displayrange=7&datatype=running
It appears the subtest is:
iconFade-close-DPI2.error.TART
Here is the pushlog on tbpl:
https://tbpl.mozilla.org/?tree=Mozilla-Beta&jobname=Ubuntu%20HW%2012.04%20mozilla-beta%20pgo%20talos%20svgr
and here is the offending changeset:
https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?changeset=0bcee2fc8e0b
There were a handful of changesets and bugs in this push, I am not sure what the root cause is, but I wanted to get this filed asap
Comment 1•11 years ago
|
||
What is the user-visible effect of this kind of regression?
Vladan, can you find somebody to help out with diagnosis here? In order to do anything about this we have to have low-risk patches landed by Monday afternoon.
Flags: needinfo?(vdjeric)
| Reporter | ||
Comment 2•11 years ago
|
||
oh, and tsvgx appears to have a 6% regression:
http://graphs.mozilla.org/graph.html#tests=%5B%5B281,53,33%5D%5D&sel=none&displayrange=7&datatype=running
appears to be in:
composite-scale.svg
Summary: 51% Linux* TART regression on Mozilla-Beta (v.34) Nov 20th from push 0bcee2fc8e0b → 51% Linux* TART|TSVGX regression on Mozilla-Beta (v.34) Nov 20th from push 0bcee2fc8e0b
Comment 3•11 years ago
|
||
This might have been bug 1101122 adding a panel to browser.xul that isn't hidden by default. I can make a very low risk patch to fix that but I don't have a linux environment suitable for testing. Who could verify this?
Comment 4•11 years ago
|
||
| Reporter | ||
Comment 5•11 years ago
|
||
We would have to do PGO builds for this. It could be done on try, we just need to have:
https://wiki.mozilla.org/ReleaseEngineering/TryChooser#What_if_I_want_PGO_for_my_build
Make sure this is from the mozilla-beta tree.
Comment 6•11 years ago
|
||
Comment 7•11 years ago
|
||
Good catch. I wish our layout code would be a little more intelligent :/ I'm quite confident the patch will fix it and it's the same I ran into with bug 1077652.
Updated•11 years ago
|
Attachment #8526985 -
Flags: review+
Attachment #8526985 -
Flags: approval-mozilla-beta+
Comment 8•11 years ago
|
||
Looks like the patch fixes the regression but we're going to roll it into some changes in bug 1101122
| Reporter | ||
Comment 9•11 years ago
|
||
thanks for putting this together so fast!
Updated•11 years ago
|
Flags: needinfo?(vdjeric)
| Reporter | ||
Comment 10•11 years ago
|
||
oh, this regression set seems much more involved and across the board:
http://alertmanager.allizom.org:8080/alerts.html?rev=0bcee2fc8e0b&table=1
| Reporter | ||
Comment 11•11 years ago
|
||
Great, I see the fix for this landed:
https://tbpl.mozilla.org/?tree=Mozilla-Beta&rev=65fa22861cad
I did a bunch of retriggers and we will see if the automation scripts detect improvements :)
| Reporter | ||
Comment 12•11 years ago
|
||
all the regressions seemed to be back to normal, thanks for jumping on this!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•