Update web-platform-tests

Update web-platform-tests

Import wpt@fed03d61ac548fb94838e0f868f75c619d9a8edb

Using update-w3c-deps in Chromium 1353ef00266c2b94ab98b1e028296c273fa14a70.

BUG=622853, 622819
Committed: https://crrev.com/135e65f5e10f02c927c85aff83baa8f8e447b635
Cr-Commit-Position: refs/heads/master@{#402318}

[Rick Byers, 2016-06-23 16:14:56]

Description was changed from

==========
Update web-platform-tests

Import wpt@fed03d61ac548fb94838e0f868f75c619d9a8edb

Using update-w3c-deps in Chromium 1353ef00266c2b94ab98b1e028296c273fa14a70.

BUG=
==========

to

==========
Update web-platform-tests

Import wpt@fed03d61ac548fb94838e0f868f75c619d9a8edb

Using update-w3c-deps in Chromium 1353ef00266c2b94ab98b1e028296c273fa14a70.

BUG=
==========

[Rick Byers, 2016-06-23 21:21:32]

Description was changed from

==========
Update web-platform-tests

Import wpt@fed03d61ac548fb94838e0f868f75c619d9a8edb

Using update-w3c-deps in Chromium 1353ef00266c2b94ab98b1e028296c273fa14a70.

BUG=
==========

to

==========
Update web-platform-tests

Import wpt@fed03d61ac548fb94838e0f868f75c619d9a8edb

Using update-w3c-deps in Chromium 1353ef00266c2b94ab98b1e028296c273fa14a70.

BUG=622853,622819
==========

[Rick Byers, 2016-06-27 15:56:33]

rbyers@chromium.org changed reviewers:
+ qyearsley@chromium.org

[Rick Byers, 2016-06-27 15:56:36]

I believe these are now all passing.  qyearsley PTAL.

[qyearsley, 2016-06-27 16:19:16]

On 2016/06/27 at 15:56:36, rbyers wrote:
> I believe these are now all passing.  qyearsley PTAL.

Thanks Rick! LGTM.

So, this change involved:

1. In W3CImportExpectations
 a Skipping newly-added top-level directories in wpt
 b Skipping specific new files that are failing for known reasons

2. In TestExpectations
 a Updating lines for renamed files
 b Adding lines for new failing tests with a known reason that already has a bug
 c Adding a line for a new failing test, and filing a new bug with more info

3. Adding new -expected.txt files for new testharness.js tests with some
failures

The parts that look easiest to automate first appear to be 1a, 2a, and 3.

[Rick Byers, 2016-06-27 18:56:24]

The CQ bit was checked by rbyers@chromium.org

[commit-bot: I haz the power, 2016-06-27 18:56:55]

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

[Rick Byers, 2016-06-27 19:03:29]

On 2016/06/27 16:19:16, qyearsley wrote:
> On 2016/06/27 at 15:56:36, rbyers wrote:
> > I believe these are now all passing.  qyearsley PTAL.
> 
> Thanks Rick! LGTM.
> 
> So, this change involved:
> 
> 1. In W3CImportExpectations
>  a Skipping newly-added top-level directories in wpt
>  b Skipping specific new files that are failing for known reasons
> 
> 2. In TestExpectations
>  a Updating lines for renamed files
>  b Adding lines for new failing tests with a known reason that already has a
bug
>  c Adding a line for a new failing test, and filing a new bug with more info
> 
> 3. Adding new -expected.txt files for new testharness.js tests with some
> failures
> 
> The parts that look easiest to automate first appear to be 1a, 2a, and 3.

Yeah.  I think the easiest way to get 1a is to rely on a directly whitelist for
import (the directories some individual/team has explicitly signed up to own).

Regarding 1b, I think that's probably unnecessary - see my
platform-predictability thread with Dirk.  We should perhaps just use
TestExpectations for this (or probably a separate file with the same
format/mechanism).

For 2a, if you think you can easily handle this, that's great!  But it may not
be worth the effort.  It should be rare and not too hard to clean up from if we
do the naive thing of just filing bugs as if there are new failing tests.

For 2b/c obviously we can't automate differentiating between these two cases.

It's still not clear to me when to prefer #3 over #2c.  Obviously if there
already is an expected file it should just be updated.  That's clearly easy to
automate.

[commit-bot: I haz the power, 2016-06-27 19:54:21]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-06-27 19:54:23]

Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[Rick Byers, 2016-06-27 20:04:56]

On 2016/06/27 19:54:23, commit-bot: I haz the power wrote:
> Try jobs failed on following builders:
>   win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

Looks like this was https://bugs.chromium.org/p/chromium/issues/detail?id=621174
- retrying.

[Rick Byers, 2016-06-27 20:05:08]

The CQ bit was checked by rbyers@chromium.org

[commit-bot: I haz the power, 2016-06-27 20:05:46]

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-06-27 21:24:55]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-06-27 21:24:57]

Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[Rick Byers, 2016-06-27 21:42:38]

On 2016/06/27 21:24:57, commit-bot: I haz the power wrote:
> Try jobs failed on following builders:
>   win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

Grrr.. Known flaky tests:
https://bugs.chromium.org/p/chromium/issues/detail?id=610300 - now disabled. 
3rd time is a charm!

[Rick Byers, 2016-06-27 21:42:53]

The CQ bit was checked by rbyers@chromium.org

[commit-bot: I haz the power, 2016-06-27 21:43:57]

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-06-27 22:50:49]

Description was changed from

==========
Update web-platform-tests

Import wpt@fed03d61ac548fb94838e0f868f75c619d9a8edb

Using update-w3c-deps in Chromium 1353ef00266c2b94ab98b1e028296c273fa14a70.

BUG=622853,622819
==========

to

==========
Update web-platform-tests

Import wpt@fed03d61ac548fb94838e0f868f75c619d9a8edb

Using update-w3c-deps in Chromium 1353ef00266c2b94ab98b1e028296c273fa14a70.

BUG=622853,622819
==========

[commit-bot: I haz the power, 2016-06-27 22:50:52]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2016-06-27 22:52:29]

Description was changed from

==========
Update web-platform-tests

Import wpt@fed03d61ac548fb94838e0f868f75c619d9a8edb

Using update-w3c-deps in Chromium 1353ef00266c2b94ab98b1e028296c273fa14a70.

BUG=622853,622819
==========

to

==========
Update web-platform-tests

Import wpt@fed03d61ac548fb94838e0f868f75c619d9a8edb

Using update-w3c-deps in Chromium 1353ef00266c2b94ab98b1e028296c273fa14a70.

BUG=622853,622819

Committed: https://crrev.com/135e65f5e10f02c927c85aff83baa8f8e447b635
Cr-Commit-Position: refs/heads/master@{#402318}
==========

[commit-bot: I haz the power, 2016-06-27 22:52:32]

Patchset 4 (id:??) landed as
https://crrev.com/135e65f5e10f02c927c85aff83baa8f8e447b635
Cr-Commit-Position: refs/heads/master@{#402318}