Import wpt@cf62b859e6b890abc34f8140d185ba91df95c5b6

Import wpt@cf62b859e6b890abc34f8140d185ba91df95c5b6

Using update-w3c-deps in Chromium 057e94297ee02e02b8ef4ff2dbe4c6f5f0914bab.

Build: https://build.chromium.org/p/chromium.infra.cron/builders/w3c-test-autoroller/builds/7895

patch from issue 2649323004 at patchset 20001 (http://crrev.com/2649323004#ps20001)

NOEXPORT=true

Review-Url: https://codereview.chromium.org/2648173006
Cr-Commit-Position: refs/heads/master@{#446613}
Committed: https://chromium.googlesource.com/chromium/src/+/e8c75f95e39c0cc7cb1a0079abdad0a26e1abe0a

[qyearsley, 2017-01-26 04:48:52]

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

[commit-bot: I haz the power, 2017-01-26 04:49:19]

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

[qyearsley, 2017-01-26 04:50:51]

Description was changed from

==========
Import wpt@cf62b859e6b890abc34f8140d185ba91df95c5b6

Using update-w3c-deps in Chromium 057e94297ee02e02b8ef4ff2dbe4c6f5f0914bab.

Build:
https://build.chromium.org/p/chromium.infra.cron/builders/w3c-test-autoroller...

patch from issue 2649323004 at patchset 20001
(http://crrev.com/2649323004#ps20001)

TBR=qyearsley@chromium.org
NOEXPORT=true
==========

to

==========
Import wpt@cf62b859e6b890abc34f8140d185ba91df95c5b6

Using update-w3c-deps in Chromium 057e94297ee02e02b8ef4ff2dbe4c6f5f0914bab.

Build:
https://build.chromium.org/p/chromium.infra.cron/builders/w3c-test-autoroller...

patch from issue 2649323004 at patchset 20001
(http://crrev.com/2649323004#ps20001)

NOEXPORT=true
==========

[qyearsley, 2017-01-26 04:50:53]

qyearsley@chromium.org changed reviewers:
+ tkent@chromium.org
- qyearsley@chromium.org

[qyearsley, 2017-01-26 04:52:02]

Alright, trying again!

Just tried to update baselines again for this one, not sure what tests will fail
-- but maybe this time it will work :-)

[tkent, 2017-01-26 05:05:35]

platform/*/external/wpt/html/semantics/embedded-content/media-elements/track/track-element/cors/*-expected.txt
contain random values generated by token() in common/utils.js.  So try bots
never succeed :-(

We should skip
html/semantics/embedded-content/media-elements/track/track-element/cors by
W3CImportExpectations or TestExpectations.

[commit-bot: I haz the power, 2017-01-26 05:50:05]

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

[commit-bot: I haz the power, 2017-01-26 05:50:06]

Dry run: Try jobs failed on following builders:
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[qyearsley, 2017-01-26 18:10:05]

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

[commit-bot: I haz the power, 2017-01-26 18:10:39]

Dry run: 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, 2017-01-26 18:15:46]

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

[commit-bot: I haz the power, 2017-01-26 18:15:49]

Dry run: Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-device-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device-xcode-...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)

[qyearsley, 2017-01-26 18:28:27]

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

[commit-bot: I haz the power, 2017-01-26 18:28:54]

Dry run: 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, 2017-01-26 18:35:13]

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

[commit-bot: I haz the power, 2017-01-26 18:35:15]

Dry run: Try jobs failed on following builders:
  android_cronet on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_cron...)
  android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...)
  chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
  ios-simulator-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-xco...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[qyearsley, 2017-01-26 20:46:27]

On 2017/01/26 at 05:05:35, tkent wrote:
>
platform/*/external/wpt/html/semantics/embedded-content/media-elements/track/track-element/cors/*-expected.txt
contain random values generated by token() in common/utils.js.  So try bots
never succeed :-(
> 
> We should skip
html/semantics/embedded-content/media-elements/track/track-element/cors by
W3CImportExpectations or TestExpectations.

In the latest patch set, I accidentally removed the https versions of the
wpt/streams tests but kept their baselines, making those tests fail, will fix
this in next patchset.

[qyearsley, 2017-01-26 23:01:03]

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

[commit-bot: I haz the power, 2017-01-26 23:02:16]

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

[ortuno, 2017-01-26 23:27:57]

https://codereview.chromium.org/2648173006/diff/60001/third_party/WebKit/Layo...
File
third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error-expected.txt
(right):

https://codereview.chromium.org/2648173006/diff/60001/third_party/WebKit/Layo...
third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error-expected.txt:1:
CONSOLE ERROR: Uncaught (in promise) NetworkError: Authentication canceled.
QQ: This seems unrelated to WPT. Why are we adding expectations for it?

[qyearsley, 2017-01-26 23:52:33]

https://codereview.chromium.org/2648173006/diff/60001/third_party/WebKit/Layo...
File
third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error-expected.txt
(right):

https://codereview.chromium.org/2648173006/diff/60001/third_party/WebKit/Layo...
third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error-expected.txt:1:
CONSOLE ERROR: Uncaught (in promise) NetworkError: Authentication canceled.
On 2017/01/26 at 23:27:57, ortuno wrote:
> QQ: This seems unrelated to WPT. Why are we adding expectations for it?

In general, this is because the auto-import process can also update
LayoutTests/resources/testharness.js, which can then add extra console errors
etc.

For example: http://crbug.com/662172

[ortuno, 2017-01-26 23:56:09]

On 2017/01/26 at 23:52:33, qyearsley wrote:
>
https://codereview.chromium.org/2648173006/diff/60001/third_party/WebKit/Layo...
> File
third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error-expected.txt
(right):
> 
>
https://codereview.chromium.org/2648173006/diff/60001/third_party/WebKit/Layo...
>
third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error-expected.txt:1:
CONSOLE ERROR: Uncaught (in promise) NetworkError: Authentication canceled.
> On 2017/01/26 at 23:27:57, ortuno wrote:
> > QQ: This seems unrelated to WPT. Why are we adding expectations for it?
> 
> In general, this is because the auto-import process can also update
LayoutTests/resources/testharness.js, which can then add extra console errors
etc.
> 
> For example: http://crbug.com/662172

I see, thanks. Should I open an issue to fix the Web Bluetooth test or do you
have one that I can assign already?

[qyearsley, 2017-01-27 00:05:06]

On 2017/01/26 at 23:56:09, ortuno wrote:
> On 2017/01/26 at 23:52:33, qyearsley wrote:
> >
https://codereview.chromium.org/2648173006/diff/60001/third_party/WebKit/Layo...
> > File
third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error-expected.txt
(right):
> > 
> >
https://codereview.chromium.org/2648173006/diff/60001/third_party/WebKit/Layo...
> >
third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error-expected.txt:1:
CONSOLE ERROR: Uncaught (in promise) NetworkError: Authentication canceled.
> > On 2017/01/26 at 23:27:57, ortuno wrote:
> > > QQ: This seems unrelated to WPT. Why are we adding expectations for it?
> > 
> > In general, this is because the auto-import process can also update
LayoutTests/resources/testharness.js, which can then add extra console errors
etc.
> > 
> > For example: http://crbug.com/662172
> 
> I see, thanks. Should I open an issue to fix the Web Bluetooth test or do you
have one that I can assign already?

I haven't filed an issue for this now, could you open one? I'm not sure if this
is the same as http://crbug.com/662172, but if it looks like it might be then do
you think it would make sense to re-open that one?

[commit-bot: I haz the power, 2017-01-27 00:18:51]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[ortuno, 2017-01-27 00:36:49]

On 2017/01/27 at 00:05:06, qyearsley wrote:
> On 2017/01/26 at 23:56:09, ortuno wrote:
> > On 2017/01/26 at 23:52:33, qyearsley wrote:
> > >
https://codereview.chromium.org/2648173006/diff/60001/third_party/WebKit/Layo...
> > > File
third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error-expected.txt
(right):
> > > 
> > >
https://codereview.chromium.org/2648173006/diff/60001/third_party/WebKit/Layo...
> > >
third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error-expected.txt:1:
CONSOLE ERROR: Uncaught (in promise) NetworkError: Authentication canceled.
> > > On 2017/01/26 at 23:27:57, ortuno wrote:
> > > > QQ: This seems unrelated to WPT. Why are we adding expectations for it?
> > > 
> > > In general, this is because the auto-import process can also update
LayoutTests/resources/testharness.js, which can then add extra console errors
etc.
> > > 
> > > For example: http://crbug.com/662172
> > 
> > I see, thanks. Should I open an issue to fix the Web Bluetooth test or do
you have one that I can assign already?
> 
> I haven't filed an issue for this now, could you open one? I'm not sure if
this is the same as http://crbug.com/662172, but if it looks like it might be
then do you think it would make sense to re-open that one?

Done http://crbug.com/685863 I'll look into it tomorrow.

[commit-bot: I haz the power, 2017-01-27 01:50:19]

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

[commit-bot: I haz the power, 2017-01-27 01:50:21]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[qyearsley, 2017-01-27 03:55:38]

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

[commit-bot: I haz the power, 2017-01-27 03:56:13]

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

[qyearsley, 2017-01-27 04:35:10]

tkent@, do you think it would be OK to commit this now? (Assuming that all try
jobs pass)

The main reason for committing now would be that this skips the .../cors tests
that have non-deterministic result text, and if this is committed now, then
theoretically the auto-import tomorrow should work.

[tkent, 2017-01-27 04:57:40]

lgtm if try bots pass.

[qyearsley, 2017-01-27 05:02:01]

On 2017/01/27 at 04:57:40, tkent wrote:
> lgtm if try bots pass.

Alright, will try to commit shortly then later we can see whether auto-import
works again; now rebasing after csswg-test update
https://codereview.chromium.org/2647353009.

[qyearsley, 2017-01-27 05:05:07]

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

[commit-bot: I haz the power, 2017-01-27 05:05:33]

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

[qyearsley, 2017-01-27 05:20:34]

The CQ bit was unchecked by qyearsley@chromium.org

[qyearsley, 2017-01-27 05:20:37]

The CQ bit was checked by qyearsley@chromium.org

[qyearsley, 2017-01-27 05:20:38]

The patchset sent to the CQ was uploaded after l-g-t-m from tkent@chromium.org
Link to the patchset: https://codereview.chromium.org/2648173006/#ps110001
(title: "Rebased")

[commit-bot: I haz the power, 2017-01-27 05:21:04]

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, 2017-01-27 06:37:07]

CQ is committing da patch.

Bot data: {"patchset_id": 110001, "attempt_start_ts": 1485494437340480,
"parent_rev": "d2961e8c0aa9e92a2cc11d53190226f823666efd", "commit_rev":
"e8c75f95e39c0cc7cb1a0079abdad0a26e1abe0a"}

[commit-bot: I haz the power, 2017-01-27 06:38:01]

Description was changed from

==========
Import wpt@cf62b859e6b890abc34f8140d185ba91df95c5b6

Using update-w3c-deps in Chromium 057e94297ee02e02b8ef4ff2dbe4c6f5f0914bab.

Build:
https://build.chromium.org/p/chromium.infra.cron/builders/w3c-test-autoroller...

patch from issue 2649323004 at patchset 20001
(http://crrev.com/2649323004#ps20001)

NOEXPORT=true
==========

to

==========
Import wpt@cf62b859e6b890abc34f8140d185ba91df95c5b6

Using update-w3c-deps in Chromium 057e94297ee02e02b8ef4ff2dbe4c6f5f0914bab.

Build:
https://build.chromium.org/p/chromium.infra.cron/builders/w3c-test-autoroller...

patch from issue 2649323004 at patchset 20001
(http://crrev.com/2649323004#ps20001)

NOEXPORT=true

Review-Url: https://codereview.chromium.org/2648173006
Cr-Commit-Position: refs/heads/master@{#446613}
Committed:
https://chromium.googlesource.com/chromium/src/+/e8c75f95e39c0cc7cb1a0079abda...
==========

[commit-bot: I haz the power, 2017-01-27 06:38:04]

Committed patchset #9 (id:110001) as
https://chromium.googlesource.com/chromium/src/+/e8c75f95e39c0cc7cb1a0079abda...