Import wpt@e1ad3cc6894b20da0a5d7dddf431c9e7848d0544

Import wpt@e1ad3cc6894b20da0a5d7dddf431c9e7848d0544

Using update-w3c-deps in Chromium f15c309c518f33f7d5bda22712f8df2e7bf77939.

BUG=

Committed: https://crrev.com/455e41a4c010219045b6a801e27cd28834bfd017
Cr-Commit-Position: refs/heads/master@{#417590}

[dtapuska, 2016-09-08 20:06:17]

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

[dtapuska, 2016-09-08 20:06:42]

dtapuska@chromium.org changed reviewers:
+ nzolghadr@chromium.org, qyearsley@chromium.org

[commit-bot: I haz the power, 2016-09-08 20:06:56]

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

[Navid Zolghadr, 2016-09-08 20:12:44]

lgtm

https://codereview.chromium.org/2322083002/diff/20001/third_party/WebKit/Layo...
File
third_party/WebKit/LayoutTests/imported/wpt/pointerevents/resources/pointerevent_attributes_hoverable_pointers-iframe.html
(left):

https://codereview.chromium.org/2322083002/diff/20001/third_party/WebKit/Layo...
third_party/WebKit/LayoutTests/imported/wpt/pointerevents/resources/pointerevent_attributes_hoverable_pointers-iframe.html:10:
</html>
A quick question here. How do we decide an html file is a test or not? I mean
for example this file in resources directory is not a test and is just something
that will be used in another test (that is not imported here and unrelated). So
is our system just ignores everything that is under resources directory when
running the tests?

[jsbell, 2016-09-08 20:37:28]

jsbell@chromium.org changed reviewers:
+ jsbell@chromium.org

[jsbell, 2016-09-08 20:37:29]

https://codereview.chromium.org/2322083002/diff/20001/third_party/WebKit/Layo...
File
third_party/WebKit/LayoutTests/imported/wpt/pointerevents/resources/pointerevent_attributes_hoverable_pointers-iframe.html
(left):

https://codereview.chromium.org/2322083002/diff/20001/third_party/WebKit/Layo...
third_party/WebKit/LayoutTests/imported/wpt/pointerevents/resources/pointerevent_attributes_hoverable_pointers-iframe.html:10:
</html>
On 2016/09/08 20:12:44, Navid Zolghadr wrote:
> A quick question here. How do we decide an html file is a test or not? I mean
> for example this file in resources directory is not a test and is just
something
> that will be used in another test (that is not imported here and unrelated).
So
> is our system just ignores everything that is under resources directory when
> running the tests?

Yes:

https://cs.chromium.org/chromium/src/third_party/WebKit/Tools/Scripts/webkitp...

The upstream web-platform-tests runner computes a manifest using more complex
logic. For the import we're looking at how we can adapt that logic:
https://bugs.chromium.org/p/chromium/issues/detail?id=505894

[commit-bot: I haz the power, 2016-09-08 21:02:57]

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

[commit-bot: I haz the power, 2016-09-08 21:02:58]

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, 2016-09-08 21:39:22]

Note, this CL was made after I did an update but before the update was reverted,
so it could only be landed as-is after relanding that CL (reland CL:
http://crrev.com/2326613004.

On 2016/09/08 at 20:37:29, jsbell wrote:
>
https://codereview.chromium.org/2322083002/diff/20001/third_party/WebKit/Layo...
> File
third_party/WebKit/LayoutTests/imported/wpt/pointerevents/resources/pointerevent_attributes_hoverable_pointers-iframe.html
(left):
> 
>
https://codereview.chromium.org/2322083002/diff/20001/third_party/WebKit/Layo...
>
third_party/WebKit/LayoutTests/imported/wpt/pointerevents/resources/pointerevent_attributes_hoverable_pointers-iframe.html:10:
</html>
> On 2016/09/08 20:12:44, Navid Zolghadr wrote:
> > A quick question here. How do we decide an html file is a test or not? I
mean
> > for example this file in resources directory is not a test and is just
something
> > that will be used in another test (that is not imported here and unrelated).
So
> > is our system just ignores everything that is under resources directory when
> > running the tests?
> 
> Yes:
> 
>
https://cs.chromium.org/chromium/src/third_party/WebKit/Tools/Scripts/webkitp...
> 
> The upstream web-platform-tests runner computes a manifest using more complex
logic. For the import we're looking at how we can adapt that logic:
https://bugs.chromium.org/p/chromium/issues/detail?id=505894

Yep. I was thinking that we'd fix this by adding a rule to our test runner to
assume that all wpt tests are ref tests or jsharness tests, and to ignore all
HTML files that don't appear to be either of those.

The other solutions may be a bit more complex; the WebKit team now uses a
resource-files.json list which includes all non-test HTML files.

[dtapuska, 2016-09-09 01:23:33]

The CQ bit was checked by dtapuska@chromium.org

[commit-bot: I haz the power, 2016-09-09 01:24:00]

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-09-09 02:15:35]

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

[commit-bot: I haz the power, 2016-09-09 02:15:36]

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_...)

[dtapuska, 2016-09-09 13:33:54]

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

[commit-bot: I haz the power, 2016-09-09 13:34:10]

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

[dtapuska, 2016-09-09 15:13:19]

The CQ bit was unchecked by dtapuska@chromium.org

[dtapuska, 2016-09-09 15:13:23]

The CQ bit was checked by dtapuska@chromium.org

[dtapuska, 2016-09-09 15:13:24]

The patchset sent to the CQ was uploaded after l-g-t-m from
nzolghadr@chromium.org
Link to the patchset: https://codereview.chromium.org/2322083002/#ps40001
(title: "Add mac exception and rebase")

[commit-bot: I haz the power, 2016-09-09 15:13:56]

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-09-09 15:40:17]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-09-09 15:42:20]

Description was changed from

==========
Import wpt@e1ad3cc6894b20da0a5d7dddf431c9e7848d0544

Using update-w3c-deps in Chromium f15c309c518f33f7d5bda22712f8df2e7bf77939.

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

to

==========
Import wpt@e1ad3cc6894b20da0a5d7dddf431c9e7848d0544

Using update-w3c-deps in Chromium f15c309c518f33f7d5bda22712f8df2e7bf77939.

BUG=

Committed: https://crrev.com/455e41a4c010219045b6a801e27cd28834bfd017
Cr-Commit-Position: refs/heads/master@{#417590}
==========

[commit-bot: I haz the power, 2016-09-09 15:42:22]

Patchset 3 (id:??) landed as
https://crrev.com/455e41a4c010219045b6a801e27cd28834bfd017
Cr-Commit-Position: refs/heads/master@{#417590}