Support both old and new MANIFEST.json formats, and update baselines.

Support both MANIFEST.json formats and update wpt test expectations.

Background: In http://crrev.com/2610243002 web-platform-tests were imported, and the Port class was updated to handle the new MANIFEST.json format. I originally believed that the new MANIFEST.json would also be committed in that CL, but it wasn't, due to file size. So tests were updated, but no tests were run because they weren't found.

Then, in http://crrev.com/2615903004, the manifest was actually updated, so tests started being run, but because of the earlier CL, the newly-imported failing tests didn't have expectations updated.

This CL adds a temporary change to the Port class to support both manifest formats, and updates test expectations.

After this CL:
 - The new MANIFEST.json should be re-added.
 - Port should be updated to support only the new format again.

BUG=678077
Review-Url: https://codereview.chromium.org/2614253003
Cr-Commit-Position: refs/heads/master@{#442354}
Committed: https://chromium.googlesource.com/chromium/src/+/2cdab23afa9bf4d85db6926da0bdae66133f3212

[qyearsley, 2017-01-06 23:29:30]

Description was changed from

==========
Import wpt@eeecf3e14368d4ab5221cde688003dedeca30dba

Using update-w3c-deps in Chromium 0f17a6c232f6e4df227e3e149c6b097957151276.

This CL (if landed directly via git cl land) would update MANIFEST.json
as well as update test expectations for newly-updated tests.

BUG=678077
==========

to

==========
Support both MANIFEST.json formats and update wpt test expectations.

Background: In http://crrev.com/2610243002 web-platform-tests were imported, and
the Port class was updated to handle the new MANIFEST.json format. I originally
believed that the new MANIFEST.json would also be committed in that CL, but it
wasn't, due to file size. So tests were updated, but no tests were run because
they weren't found.

Then, in http://crrev.com/2615903004, the manifest was actually updated, so
tests started being run, but because of the earlier CL, the newly-imported
failing tests didn't have expectations updated.

This CL adds a temporary change to the Port class to support both manifest
formats, and updates test expectations.

After this CL:
 - The new MANIFEST.json should be re-added.
 - Port should be updated to support only the new format again.

BUG=678077
==========

[qyearsley, 2017-01-06 23:29:30]

qyearsley@chromium.org changed reviewers:
+ dpranke@chromium.org, jsbell@chromium.org

[qyearsley, 2017-01-07 20:08:43]

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

[commit-bot: I haz the power, 2017-01-07 20:08:51]

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-07 21:20:24]

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

[commit-bot: I haz the power, 2017-01-07 21:20:25]

Dry run: This issue passed the CQ dry run.

[Dirk Pranke, 2017-01-09 03:31:01]

lgtm

[qyearsley, 2017-01-09 17:07:26]

The CQ bit was checked by qyearsley@chromium.org

[commit-bot: I haz the power, 2017-01-09 17:07:44]

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-09 18:25:44]

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

[commit-bot: I haz the power, 2017-01-09 18:25:45]

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

[qyearsley, 2017-01-09 18:48:01]

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

[commit-bot: I haz the power, 2017-01-09 18:48:23]

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-09 19:56:55]

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

[commit-bot: I haz the power, 2017-01-09 19:56:56]

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_...)
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[qyearsley, 2017-01-09 20:12:40]

The CQ bit was checked by qyearsley@chromium.org

[qyearsley, 2017-01-09 20:12:40]

The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org
Link to the patchset: https://codereview.chromium.org/2614253003/#ps40001
(title: "Update
imported/wpt/html/browsers/origin/cross-origin-objects/cross-origin-objects-exceptions-expec…")

[commit-bot: I haz the power, 2017-01-09 20:13: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, 2017-01-09 21:29:10]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1483992760419030,
"parent_rev": "2267cfcce06c92602376754343e5f45effeee1f1", "commit_rev":
"2cdab23afa9bf4d85db6926da0bdae66133f3212"}

[commit-bot: I haz the power, 2017-01-09 21:29:42]

Description was changed from

==========
Support both MANIFEST.json formats and update wpt test expectations.

Background: In http://crrev.com/2610243002 web-platform-tests were imported, and
the Port class was updated to handle the new MANIFEST.json format. I originally
believed that the new MANIFEST.json would also be committed in that CL, but it
wasn't, due to file size. So tests were updated, but no tests were run because
they weren't found.

Then, in http://crrev.com/2615903004, the manifest was actually updated, so
tests started being run, but because of the earlier CL, the newly-imported
failing tests didn't have expectations updated.

This CL adds a temporary change to the Port class to support both manifest
formats, and updates test expectations.

After this CL:
 - The new MANIFEST.json should be re-added.
 - Port should be updated to support only the new format again.

BUG=678077
==========

to

==========
Support both MANIFEST.json formats and update wpt test expectations.

Background: In http://crrev.com/2610243002 web-platform-tests were imported, and
the Port class was updated to handle the new MANIFEST.json format. I originally
believed that the new MANIFEST.json would also be committed in that CL, but it
wasn't, due to file size. So tests were updated, but no tests were run because
they weren't found.

Then, in http://crrev.com/2615903004, the manifest was actually updated, so
tests started being run, but because of the earlier CL, the newly-imported
failing tests didn't have expectations updated.

This CL adds a temporary change to the Port class to support both manifest
formats, and updates test expectations.

After this CL:
 - The new MANIFEST.json should be re-added.
 - Port should be updated to support only the new format again.

BUG=678077

Review-Url: https://codereview.chromium.org/2614253003
Cr-Commit-Position: refs/heads/master@{#442354}
Committed:
https://chromium.googlesource.com/chromium/src/+/2cdab23afa9bf4d85db6926da0bd...
==========

[commit-bot: I haz the power, 2017-01-09 21:29:43]

Committed patchset #5 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/2cdab23afa9bf4d85db6926da0bd...