Talos Regression :( Tp4 Mobile NoChrome increase 5.55% on Android 2.2 mobile

Nobody

unread,

Sep 14, 2011, 10:06:16 AM9/14/11

to dev-tree-...@lists.mozilla.org

Regression :( Tp4 Mobile NoChrome increase 5.55% on Android 2.2 mobile
----------------------------------------------------------------------
Previous: avg 528.647 stddev 13.777 of 30 runs up to revision 569a45bfb71c
New : avg 557.970 stddev 2.494 of 5 runs since revision 569a45bfb71c
Change : +29.323 (5.55% / z=2.128)
Graph : http://mzl.la/p22Znc

Changeset range: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=569a45bfb71c&tochange=569a45bfb71c

Matt Brubeck

unread,

Sep 14, 2011, 10:55:27 AM9/14/11

to Geoff Brown

On 09/14/2011 07:06 AM, Nobody wrote:
> Regression :( Tp4 Mobile NoChrome increase 5.55% on Android 2.2 mobile
> ----------------------------------------------------------------------
> Previous: avg 528.647 stddev 13.777 of 30 runs up to revision 569a45bfb71c
> New : avg 557.970 stddev 2.494 of 5 runs since revision 569a45bfb71c
> Change : +29.323 (5.55% / z=2.128)
> Graph : http://mzl.la/p22Znc

It looks like this regression appeared first on mozilla-inbound:
http://graphs-new.mozilla.org/graph.html#tests=[[84,11,20],[84,63,20]]&sel=none&displayrange=7&datatype=running

In the following regression range:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=f08b80318718&tochange=d469840a370f

Could this be caused by bug 661900?

Ehsan Akhgari

unread,

Sep 14, 2011, 1:34:03 PM9/14/11

to Matt Brubeck, dev-tree-...@lists.mozilla.org

It's possible. I will try backing it out to see whether it helps.

--
Ehsan
<http://ehsanakhgari.org/>

On Wed, Sep 14, 2011 at 10:55 AM, Matt Brubeck <mbru...@mozilla.com> wrote:

> On 09/14/2011 07:06 AM, Nobody wrote:
>
>> Regression :( Tp4 Mobile NoChrome increase 5.55% on Android 2.2 mobile

>> ------------------------------**------------------------------**

>> ----------
>> Previous: avg 528.647 stddev 13.777 of 30 runs up to revision
>> 569a45bfb71c
>> New : avg 557.970 stddev 2.494 of 5 runs since revision
>> 569a45bfb71c
>> Change : +29.323 (5.55% / z=2.128)
>> Graph : http://mzl.la/p22Znc
>>
>
> It looks like this regression appeared first on mozilla-inbound:

> http://graphs-new.mozilla.org/**graph.html#tests=[[84,11,20],[**
> 84,63,20]]&sel=none&**displayrange=7&datatype=**running<http://graphs-new.mozilla.org/graph.html#tests=[[84,11,20],[84,63,20]]&sel=none&displayrange=7&datatype=running>

>
> In the following regression range:

> https://hg.mozilla.org/**integration/mozilla-inbound/**
> pushloghtml?fromchange=**f08b80318718&tochange=**d469840a370f<https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=f08b80318718&tochange=d469840a370f>

>
> Could this be caused by bug 661900?
>

> ______________________________**_________________
> dev-tree-management mailing list
> dev-tree-management@lists.**mozilla.org<dev-tree-...@lists.mozilla.org>
> https://lists.mozilla.org/**listinfo/dev-tree-management<https://lists.mozilla.org/listinfo/dev-tree-management>
>

Ehsan Akhgari

unread,

Sep 15, 2011, 9:54:35 AM9/15/11

to

So, the regression detection scripts didn't catch anything here, but I
see the mozilla-inbound nodes on the graph going down. Am I just
imagining things?!

Note that I just merged the backout changeset to mozilla-central, so
we can see if it will follow the trend.

Ehsan

On Sep 14, 1:34 pm, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote:
> It's possible. I will try backing it out to see whether it helps.
>
> --
> Ehsan
> <http://ehsanakhgari.org/>
>
>
>
>
>
>
>
> On Wed, Sep 14, 2011 at 10:55 AM, Matt Brubeck <mbrub...@mozilla.com> wrote:
> > On 09/14/2011 07:06 AM, Nobody wrote:
>
> >> Regression :( Tp4 Mobile NoChrome increase 5.55% on Android 2.2 mobile
> >> ------------------------------**------------------------------**
> >> ----------
> >> Previous: avg 528.647 stddev 13.777 of 30 runs up to revision
> >> 569a45bfb71c
> >> New : avg 557.970 stddev 2.494 of 5 runs since revision
> >> 569a45bfb71c
> >> Change : +29.323 (5.55% / z=2.128)
> >> Graph :http://mzl.la/p22Znc
>
> > It looks like this regression appeared first on mozilla-inbound:
> >http://graphs-new.mozilla.org/**graph.html#tests=[[84,11,20],[**
> > 84,63,20]]&sel=none&**displayrange=7&datatype=**running<http://graphs-new.mozilla.org/graph.html#tests=[[84,11,20],[84,63,20]]&sel=none&displayrange=7&datatype=running>
>
> > In the following regression range:
> >https://hg.mozilla.org/**integration/mozilla-inbound/**

> > pushloghtml?fromchange=**f08b80318718&tochange=**d469840a370f<https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromch...>

>
> > Could this be caused by bug 661900?
>
> > ______________________________**_________________
> > dev-tree-management mailing list

> > dev-tree-management@lists.**mozilla.org<dev-tree-managem...@lists.mozilla.org>
> >https://lists.mozilla.org/**listinfo/dev-tree-management<https://lists.mozilla.org/listinfo/dev-tree-management>