Change bug number of paint/selection/seleciton-within-composited-scroller.html

Change bug number of paint/selection/seleciton-within-composited-scroller.html

It's not bug 536999 causing the test needing manual rebaseline.
Bug 570401 is.

BUG=570401
TBR=noel@chromium.org

Committed: https://crrev.com/de21252d473ce0180462fc4d3e83e38288653d11
Cr-Commit-Position: refs/heads/master@{#366407}

[commit-bot: I haz the power, 2015-12-21 17:40:08]

Description was changed from

==========
Change bug number of paint/selection/seleciton-within-composited-scroller.html

It's not bug 536999 causing the test needing manual rebaseline.
Bug 570401 is.

BUG=570401
TBR=noel@chromium.org
==========

to

==========
Change bug number of paint/selection/seleciton-within-composited-scroller.html

It's not bug 536999 causing the test needing manual rebaseline.
Bug 570401 is.

BUG=570401
TBR=noel@chromium.org

Committed: https://crrev.com/de21252d473ce0180462fc4d3e83e38288653d11
Cr-Commit-Position: refs/heads/master@{#366407}
==========

[commit-bot: I haz the power, 2015-12-21 17:40:10]

Patchset 1 (id:??) landed as
https://crrev.com/de21252d473ce0180462fc4d3e83e38288653d11
Cr-Commit-Position: refs/heads/master@{#366407}

[Noel Gordon, 2015-12-21 22:40:13]

LGTM - the test lost its scroll bars, iirc, so that might have been some other
issue.  That's why I retained the original bug number...

[Xianzhu, 2015-12-21 22:57:15]

On 2015/12/21 22:40:13, noel gordon wrote:
> LGTM - the test lost its scroll bars, iirc, so that might have been some other
> issue.  That's why I retained the original bug number...

Can you provide more information about "the test lost its scroll bars", e.g.
link to the bot result?

[Noel Gordon, 2015-12-21 23:34:38]

On 2015/12/21 22:57:15, Xianzhu wrote:
> On 2015/12/21 22:40:13, noel gordon wrote:
> > LGTM - the test lost its scroll bars, iirc, so that might have been some
other
> > issue.  That's why I retained the original bug number...
> 
> Can you provide more information about "the test lost its scroll bars", e.g.
> link to the bot result?

https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Mac10_6/4...

is the example I recall.  According to the flakyness dashboard, the test bounced
recently

http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=pai...

[Xianzhu, 2015-12-21 23:42:50]

On 2015/12/21 23:34:38, noel gordon wrote:
> On 2015/12/21 22:57:15, Xianzhu wrote:
> > On 2015/12/21 22:40:13, noel gordon wrote:
> > > LGTM - the test lost its scroll bars, iirc, so that might have been some
> other
> > > issue.  That's why I retained the original bug number...
> > 
> > Can you provide more information about "the test lost its scroll bars", e.g.
> > link to the bot result?
> 
>
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Mac10_6/4...
> 
> is the example I recall.

The actual result is correct. I still didn't see "the test lost its scroll
bars".

> According to the flakyness dashboard, the test bounced
> recently
> 
>
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=pai...

I think this is because of bug 570401 which caused the auto-rebaseline bot
failed to get the correct baseline.

[Noel Gordon, 2015-12-22 00:07:27]

On 2015/12/21 23:42:50, Xianzhu wrote:
> On 2015/12/21 23:34:38, noel gordon wrote:
> > On 2015/12/21 22:57:15, Xianzhu wrote:
> > > On 2015/12/21 22:40:13, noel gordon wrote:
> > > > LGTM - the test lost its scroll bars, iirc, so that might have been some
> > other
> > > > issue.  That's why I retained the original bug number...
> > > 
> > > Can you provide more information about "the test lost its scroll bars",
e.g.
> > > link to the bot result?
> > 
> >
>
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Mac10_6/4...
> > 
> > is the example I recall.
> 
> The actual result is correct. I still didn't see "the test lost its scroll
> bars".

Gardeners looks at diffs when lots of tree brokenness is active and too little
time to debug individual tests that should not have changed behavior in the
first place.

https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Mac10_6/4...

"Something" changed with scroll bars.

[Noel Gordon, 2015-12-22 00:09:01]

On 2015/12/21 23:42:50, Xianzhu wrote:
> > According to the flakyness dashboard, the test bounced
> > recently
> > 
> >
>
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=pai...
> 
> I think this is because of bug 570401 which caused the auto-rebaseline bot
> failed to get the correct baseline.

Yeah possible, dunno.  We'll find out for sure once the rebaseline-server is
back in business.

[Xianzhu, 2015-12-22 00:10:49]

On 2015/12/22 00:07:27, noel gordon wrote:
> On 2015/12/21 23:42:50, Xianzhu wrote:
> > On 2015/12/21 23:34:38, noel gordon wrote:
> > > On 2015/12/21 22:57:15, Xianzhu wrote:
> > > > On 2015/12/21 22:40:13, noel gordon wrote:
> > > > > LGTM - the test lost its scroll bars, iirc, so that might have been
some
> > > other
> > > > > issue.  That's why I retained the original bug number...
> > > > 
> > > > Can you provide more information about "the test lost its scroll bars",
> e.g.
> > > > link to the bot result?
> > > 
> > >
> >
>
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Mac10_6/4...
> > > 
> > > is the example I recall.
> > 
> > The actual result is correct. I still didn't see "the test lost its scroll
> > bars".
> 
> Gardeners looks at diffs when lots of tree brokenness is active and too little
> time to debug individual tests that should not have changed behavior in the
> first place.
> 
>
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Mac10_6/4...
> 
> "Something" changed with scroll bars.

This seems a different test that this CL involves.