W3C import: Update manifest-updating step after upstream changes.

W3C import: Update manifest-updating step after upstream changes.

Background: The recent change https://github.com/w3c/web-platform-tests/commit/758f6c45dd335e276ab822ef5d96ac31398b76e9 updated wpt-tools to include https://github.com/w3c/wpt-tools/commit/8777171a5568e9fa967ef7a807dc400d89a07637, which changed some things about the manifest format and also the way that the manifest update is done.

After that change, the manifest update script looked at all files in the current repo, which in our case is the whole Chromium repo. This CL resolves this by passing the flag --work to the manifest script.

BUG=678077
Committed: https://crrev.com/787a1e7a701b094d4c208820f94b3830b35515f3
Cr-Commit-Position: refs/heads/master@{#441499}

[qyearsley, 2017-01-04 20:52:29]

Description was changed from

==========
W3C import: Update manifest-updating step after upstream changes.

https://github.com/w3c/web-platform-tests/commit/758f6c45dd335e276ab822ef5d96...

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

to

==========
W3C import: Update manifest-updating step after upstream changes.

Background: The recent change
https://github.com/w3c/web-platform-tests/commit/758f6c45dd335e276ab822ef5d96...
updated wpt-tools to include
https://github.com/w3c/wpt-tools/commit/8777171a5568e9fa967ef7a807dc400d89a07637,
which changed some things about the manifest format and also the way that the
manifest update is done.

After that change, the manifest update script looked at all files in the current
repo, which in our case is the whole Chromium repo. This CL resolves this by
passing the flag --work to the manifest script.

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

[qyearsley, 2017-01-04 20:52:30]

qyearsley@chromium.org changed reviewers:
+ jeffcarp@chromium.org, tkent@chromium.org

[qyearsley, 2017-01-04 20:52:35]

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

[commit-bot: I haz the power, 2017-01-04 20:52:53]

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

[jeffcarp, 2017-01-04 22:07:47]

lgtm

[commit-bot: I haz the power, 2017-01-04 22:22:00]

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

[commit-bot: I haz the power, 2017-01-04 22:22:01]

Dry run: This issue passed the CQ dry run.

[qyearsley, 2017-01-04 22:45:15]

The CQ bit was checked by qyearsley@chromium.org

[commit-bot: I haz the power, 2017-01-04 22:45:42]

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-04 22:51:16]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1483569915232820, "parent_rev":
"b7a91528f838b77f137f07aae530618f902e62bd", "commit_rev":
"7605d92317b27670fe0ceaebb875ab42d129811f"}

[commit-bot: I haz the power, 2017-01-04 22:51:46]

Description was changed from

==========
W3C import: Update manifest-updating step after upstream changes.

Background: The recent change
https://github.com/w3c/web-platform-tests/commit/758f6c45dd335e276ab822ef5d96...
updated wpt-tools to include
https://github.com/w3c/wpt-tools/commit/8777171a5568e9fa967ef7a807dc400d89a07637,
which changed some things about the manifest format and also the way that the
manifest update is done.

After that change, the manifest update script looked at all files in the current
repo, which in our case is the whole Chromium repo. This CL resolves this by
passing the flag --work to the manifest script.

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

to

==========
W3C import: Update manifest-updating step after upstream changes.

Background: The recent change
https://github.com/w3c/web-platform-tests/commit/758f6c45dd335e276ab822ef5d96...
updated wpt-tools to include
https://github.com/w3c/wpt-tools/commit/8777171a5568e9fa967ef7a807dc400d89a07637,
which changed some things about the manifest format and also the way that the
manifest update is done.

After that change, the manifest update script looked at all files in the current
repo, which in our case is the whole Chromium repo. This CL resolves this by
passing the flag --work to the manifest script.

BUG=678077

Review-Url: https://codereview.chromium.org/2613753002
==========

[commit-bot: I haz the power, 2017-01-04 22:51:47]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2017-01-04 22:54:30]

Description was changed from

==========
W3C import: Update manifest-updating step after upstream changes.

Background: The recent change
https://github.com/w3c/web-platform-tests/commit/758f6c45dd335e276ab822ef5d96...
updated wpt-tools to include
https://github.com/w3c/wpt-tools/commit/8777171a5568e9fa967ef7a807dc400d89a07637,
which changed some things about the manifest format and also the way that the
manifest update is done.

After that change, the manifest update script looked at all files in the current
repo, which in our case is the whole Chromium repo. This CL resolves this by
passing the flag --work to the manifest script.

BUG=678077

Review-Url: https://codereview.chromium.org/2613753002
==========

to

==========
W3C import: Update manifest-updating step after upstream changes.

Background: The recent change
https://github.com/w3c/web-platform-tests/commit/758f6c45dd335e276ab822ef5d96...
updated wpt-tools to include
https://github.com/w3c/wpt-tools/commit/8777171a5568e9fa967ef7a807dc400d89a07637,
which changed some things about the manifest format and also the way that the
manifest update is done.

After that change, the manifest update script looked at all files in the current
repo, which in our case is the whole Chromium repo. This CL resolves this by
passing the flag --work to the manifest script.

BUG=678077

Committed: https://crrev.com/787a1e7a701b094d4c208820f94b3830b35515f3
Cr-Commit-Position: refs/heads/master@{#441499}
==========

[commit-bot: I haz the power, 2017-01-04 22:54:30]

Patchset 1 (id:??) landed as
https://crrev.com/787a1e7a701b094d4c208820f94b3830b35515f3
Cr-Commit-Position: refs/heads/master@{#441499}