Closed
Bug 976563
Opened 11 years ago
Closed 11 years ago
Talos rck2 (300%+) regression due to bug 941995
Categories
(Firefox for Android Graveyard :: Toolbar, defect)
Tracking
(firefox29 unaffected, firefox30 fixed, firefox31 fixed, fennec30+)
RESOLVED
FIXED
Firefox 31
Tracking | Status | |
---|---|---|
firefox29 | --- | unaffected |
firefox30 | --- | fixed |
firefox31 | --- | fixed |
fennec | 30+ | --- |
People
(Reporter: kats, Assigned: kats)
References
Details
(Whiteboard: [talos_regression])
Attachments
(1 file)
1.42 KB,
patch
|
wesj
:
review+
|
Details | Diff | Splinter Review |
I landed bug 941995 and got Talos regression notifications (http://mzl.la/1erXQgn and http://mzl.la/1fAUr3v) that indicated regressions from that change to the rck2 test.
The rck2 test loads a canned CNN page and simulates a bunch of user-driven panning/zooming actions on it. The CNN page has a meta-viewport tag [1] that says width=1024, so the patches on bug 941995 should only make a difference if the device the test is running on has a screen width of 1024 or higher. (IIRC the Tegras satisfy this criteria - gbrown, can you confirm?).
Assuming this is what is happening, we have three options that I can think of:
1) Do nothing - declare the user input now performs a different set of user actions than before by design, and declare a new baseline value for the test
2) Change the meta-viewport tag in the canned CNN page to have a wider viewport width, thereby restoring the double-tap-to-zoom behaviour on it. However changing the viewport width will probably again mean that pinches and such will behave differently than they did before, and so there is no guarantee that this will improve the numbers at all. It's basically trading one random baseline for another.
3) Implement some "escape mechanism" as wesj suggested at [2] and updated the canned CNN page to use it. This will likely bring us our old numbers back.
[1] http://hg.mozilla.org/build/talos/file/7674ffd4b494/talos/startup_test/fennecmark/cnn/cnn.com/index.html#l14
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=941995#c4
![]() |
||
Comment 1•11 years ago
|
||
The tegra screen width is 1024. (1024 x 768)
Assignee | ||
Comment 2•11 years ago
|
||
Thanks.
Wes, did you have any thoughts on the "escape mechanism" to get back the double-tap delay?
Flags: needinfo?(wjohnston)
Updated•11 years ago
|
Whiteboard: [talos_regression]
Comment 3•11 years ago
|
||
So just to be clear, the problem is that the tests test double-tap zoom and because of the new viewport stuff, double tap is disabled on it?
I think we should just add a (-moz-?)enable-double-tap-zoom arg to the viewport tag. If its set, double tap is enabled, regardless of other tags like user-scalable or width.
Assignee | ||
Comment 4•11 years ago
|
||
(In reply to Wesley Johnston (:wesj) from comment #3)
> So just to be clear, the problem is that the tests test double-tap zoom and
> because of the new viewport stuff, double tap is disabled on it?
Yeah, basically. The talos test simulates user input sequences which includes double-tap, and that doesn't work any more.
> I think we should just add a (-moz-?)enable-double-tap-zoom arg to the
> viewport tag. If its set, double tap is enabled, regardless of other tags
> like user-scalable or width.
Hm, ok. I don't have any particularly strong feelings about this either way. Adding mbrubeck also in case he has any objections.
Comment 5•11 years ago
|
||
FWIW, I think we could just alter the test here though.
I've wondered if its users on tablets would be more frustrated with us disabling double-tap zoom there...
Flags: needinfo?(wjohnston)
Assignee | ||
Comment 6•11 years ago
|
||
Alter the test in what way? If you're referring to option (2) in comment 0 then I don't think that's going to help with the numbers and I would rather just leave everything as-is.
![]() |
||
Comment 7•11 years ago
|
||
It looks like this is now on aurora:
Regression: Mozilla-Aurora - Robocop Checkerboarding Real User Benchmark - Android 2.2 (Native) - 791% increase
---------------------------------------------------------------------------------------------------------------
Previous: avg 2.738 stddev 0.272 of 12 runs up to revision 07f5580d8a54
New : avg 24.397 stddev 4.346 of 12 runs since revision c0befb3c8038
Change : +21.659 (791% / z=79.541)
Graph : http://mzl.la/1dg6mp5
Changeset range: http://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?fromchange=07f5580d8a54&tochange=c0befb3c8038
tracking-fennec: --- → ?
Updated•11 years ago
|
Assignee: nobody → wjohnston
tracking-fennec: ? → 30+
Comment 8•11 years ago
|
||
are we concerned about this? I want to make sure we address this during Aurora instead of waiting for we uplift to Beta.
Assignee | ||
Comment 9•11 years ago
|
||
I am not. I think we should just accept the new baseline value and close this bug.
Comment 10•11 years ago
|
||
we don't have a new baseline anymore, we have a bunch of random data points:
http://graphs.mozilla.org/graph.html#tests=[[201,52,20],[201,63,20]]&sel=none&displayrange=90&datatype=running
So at the moment this test is not very useful- should we fix the test, or disable it?
Comment 11•11 years ago
|
||
I mostly agree with kats. I don't have time to dig into this right now, and given we know why it happened, its not a high priority for me.
I don't really know where this test is though. Can we just disable the doubletap zoom part of this?
Comment 12•11 years ago
|
||
Assignee | ||
Comment 13•11 years ago
|
||
(In reply to Joel Maher (:jmaher) from comment #10)
> we don't have a new baseline anymore, we have a bunch of random data points:
> http://graphs.mozilla.org/graph.html#tests=[[201,52,20],[201,63,
> 20]]&sel=none&displayrange=90&datatype=running
>
> So at the moment this test is not very useful- should we fix the test, or
> disable it?
Ah, I hadn't seen that! Yeah in that case we should do something about it.
Assignee | ||
Comment 14•11 years ago
|
||
Pending try run at https://tbpl.mozilla.org/?tree=Try&rev=6906614ed8bc to verify it restores the old baseline.
I also pushed https://tbpl.mozilla.org/?tree=Try&rev=63935199056b earlier which disables the code that introduced this change, to verify that there weren't any other talos regressions in the meantime, and to make sure the attached patch results in the same behaviour.
Assignee: wjohnston → bugmail.mozilla
Attachment #8401005 -
Flags: review?(wjohnston)
Comment 15•11 years ago
|
||
Comment on attachment 8401005 [details] [diff] [review]
Force-enable double-tap zooming in the talos test
Review of attachment 8401005 [details] [diff] [review]:
-----------------------------------------------------------------
Oh nice!
Attachment #8401005 -
Flags: review?(wjohnston) → review+
Assignee | ||
Comment 16•11 years ago
|
||
Comment 17•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 31
Assignee | ||
Comment 18•11 years ago
|
||
Comment on attachment 8401005 [details] [diff] [review]
Force-enable double-tap zooming in the talos test
[Approval Request Comment]
Bug caused by (feature/regressing bug #): bug 941995
User impact if declined: this talos regression might hide other real regressions. this regression itself has no direct user impact as it is test-only
Testing completed (on m-c, etc.): on m-c now
Risk to taking this patch (and alternatives if risky): low risk, test only
String or IDL/UUID changes made by this patch: none
Attachment #8401005 -
Flags: approval-mozilla-aurora?
Comment 19•11 years ago
|
||
I am not seeing any difference in the results yet, also are we looking to backport this to Aurora, as this is a test only it doesn't seem critical, but we should just disable this test on firefox 30 as it is not yielding anything useful right now.
Assignee | ||
Comment 20•11 years ago
|
||
I got emails from the bot saying things were better:
http://graphs.mozilla.org/graph.html#tests=[[201,64,20]]&sel=1396800459000,1396973259000&displayrange=7&datatype=running
http://graphs.mozilla.org/graph.html#tests=[[201,64,29]]&sel=1396800843000,1396973643000
Assignee | ||
Comment 21•11 years ago
|
||
And I would rather uplift the fix so that it doesn't obscure other real regressions from future uplifts.
Comment 22•11 years ago
|
||
oh, you win!
Comment 23•11 years ago
|
||
Comment on attachment 8401005 [details] [diff] [review]
Force-enable double-tap zooming in the talos test
this can be landed as a=test-only
Attachment #8401005 -
Flags: approval-mozilla-aurora?
Assignee | ||
Comment 24•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•