Import wpt@357b83b809e3cbc7a1805e7c3ca108a7980d782f

Import wpt@357b83b809e3cbc7a1805e7c3ca108a7980d782f

Using update-w3c-deps in Chromium 8be2f0889cd2d57cfd9910279e4b2e697aba76f8.

Patch from issue 2401083002 at patchset 1 (http://crrev.com/2401083002#ps1)

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

[qyearsley, 2016-10-10 20:31:27]

qyearsley@chromium.org changed reviewers:
+ jsbell@chromium.org, suzyh@chromium.org, tkent@chromium.org

[qyearsley, 2016-10-10 20:31:28]

I'm doing a somewhat manual-ish WPT import now since some changes have been
building up (the w3c-test-autoroller won't be able to complete this import until
http://crbug.com/654030 is resolved).

[jsbell, 2016-10-10 21:39:43]

Any idea what's up with the Win failures?

[suzyh_UTC10 (ex-contributor), 2016-10-10 21:53:59]

web-animations lgtm

[jsbell, 2016-10-10 22:18:35]

On 2016/10/10 21:39:43, jsbell wrote:
> Any idea what's up with the Win failures?

Hrm, they also fail w/o the patch:
https://build.chromium.org/p/tryserver.blink/builders/win7_blink_rel/builds/1078

... yet the flakiness dashboard doesn't show them, and they're not failing in
randomly selected other builds..

[qyearsley, 2016-10-10 22:23:20]

On 2016/10/10 at 22:18:35, jsbell wrote:
> On 2016/10/10 21:39:43, jsbell wrote:
> > Any idea what's up with the Win failures?
> 
> Hrm, they also fail w/o the patch:
https://build.chromium.org/p/tryserver.blink/builders/win7_blink_rel/builds/1078
> 
> ... yet the flakiness dashboard doesn't show them, and they're not failing in
randomly selected other builds..

Ah, that's what I thought when I saw that at first too, but on second look I
think that those tests all passed without the patch, and looking at the results,
it's a mismatch with the baseline; I think that something went wrong with
rebaselining :-/

[qyearsley, 2016-10-10 22:27:46]

On 2016/10/10 at 22:23:20, qyearsley wrote:
> On 2016/10/10 at 22:18:35, jsbell wrote:
> > On 2016/10/10 21:39:43, jsbell wrote:
> > > Any idea what's up with the Win failures?
> > 
> > Hrm, they also fail w/o the patch:
https://build.chromium.org/p/tryserver.blink/builders/win7_blink_rel/builds/1078
> > 
> > ... yet the flakiness dashboard doesn't show them, and they're not failing
in randomly selected other builds..
> 
> Ah, that's what I thought when I saw that at first too, but on second look I
think that those tests all passed without the patch, and looking at the results,
it's a mismatch with the baseline; I think that something went wrong with
rebaselining :-/

Now ran ./webkit-patch rebaseline-cl --only-changed-tests again, which may have
fixed it (it re-downloaded the actual win7 results and then optimized baselines,
which resulted in the added win7 baselines being deleted); restarting try jobs.

[jsbell, 2016-10-10 22:29:57]

On 2016/10/10 22:27:46, qyearsley wrote:
> Now ran ./webkit-patch rebaseline-cl --only-changed-tests again, which may
have
> fixed it (it re-downloaded the actual win7 results and then optimized
baselines,
> which resulted in the added win7 baselines being deleted); restarting try
jobs.

Assuming that fixes it, rs lgtm

(TestExpectations and IndexedDB inspected in detail)

[qyearsley, 2016-10-10 22:57:51]

The CQ bit was checked by qyearsley@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-10 22:58:10]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[qyearsley, 2016-10-11 00:22:16]

The CQ bit was checked by qyearsley@chromium.org

[qyearsley, 2016-10-11 00:22:17]

The patchset sent to the CQ was uploaded after l-g-t-m from suzyh@chromium.org,
jsbell@chromium.org
Link to the patchset: https://codereview.chromium.org/2408493002/#ps80001
(title: "Added one more win7-specific baseline")

[commit-bot: I haz the power, 2016-10-11 00:22:34]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-11 02:40:59]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2016-10-11 02:45:00]

Description was changed from

==========
Import wpt@357b83b809e3cbc7a1805e7c3ca108a7980d782f

Using update-w3c-deps in Chromium 8be2f0889cd2d57cfd9910279e4b2e697aba76f8.

Patch from issue 2401083002 at patchset 1 (http://crrev.com/2401083002#ps1)
==========

to

==========
Import wpt@357b83b809e3cbc7a1805e7c3ca108a7980d782f

Using update-w3c-deps in Chromium 8be2f0889cd2d57cfd9910279e4b2e697aba76f8.

Patch from issue 2401083002 at patchset 1 (http://crrev.com/2401083002#ps1)

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

[commit-bot: I haz the power, 2016-10-11 02:45:02]

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

[loyso (OOO), 2016-10-11 06:09:11]

A revert of this CL (patchset #5 id:80001) has been created in
https://codereview.chromium.org/2408083002/ by loyso@chromium.org.

The reason for reverting is: Breaks WebKit tests
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Mac10.11%20%28....