Reland of wptserve: Enable WPTServe by default.

Reland of wptserve: Enable WPTServe by default. (patchset #1 id:1 of https://codereview.chromium.org/2537413002/ )

Reason for revert:
The problem was resolved.


Original issue's description:
> Revert of wptserve: Enable WPTServe by default. (patchset #1 id:1 of https://codereview.chromium.org/2497193002/ )
> 
> Reason for revert:
> I suspect that the startup/shutdown logic in wptserve is not right, and we're seeing intermittent failures where we're hanging trying to start wptserve.
> 
> See crbug.com/669194 and https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Mac10.11/builds/13447/steps/webkit_tests/logs/stdio for an example.
> 
> I'm speculatively reverting this for now, to see if things become happier.
> 
> Original issue's description:
> > Reland of wptserve: Enable WPTServe by default.
> 
> TBR=qyearsley@chromium.org,jsbell@chromium.org,tkent@chromium.org
> NOTRY=true
> NOPRESUBMIT=true
> BUG=618366
> 
> Committed: https://crrev.com/b5ce7e0a17e32d6d145124938a90220e9f9990c5
> Cr-Commit-Position: refs/heads/master@{#435129}

TBR=qyearsley@chromium.org,jsbell@chromium.org,dpranke@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=618366
Review-Url: https://codereview.chromium.org/2633083002
Cr-Commit-Position: refs/heads/master@{#443953}
Committed: https://chromium.googlesource.com/chromium/src/+/01c97b5106a69c02931e5aee55e460e1e7eb398a

[tkent, 2017-01-16 03:38:15]

Created Reland of wptserve: Enable WPTServe by default.

[tkent, 2017-01-16 03:39:01]

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

[commit-bot: I haz the power, 2017-01-16 03:39:08]

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-16 04:54:03]

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

[commit-bot: I haz the power, 2017-01-16 04:54:03]

Dry run: This issue passed the CQ dry run.

[tkent, 2017-01-16 22:22:16]

The CQ bit was checked by tkent@chromium.org

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

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-16 22:26:49]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1484605336502500, "parent_rev":
"3d5304ee300fa14d75bc8b2cdf920c0aa7acf73b", "commit_rev":
"01c97b5106a69c02931e5aee55e460e1e7eb398a"}

[commit-bot: I haz the power, 2017-01-16 22:27:18]

Description was changed from

==========
Reland of wptserve: Enable WPTServe by default. (patchset #1 id:1 of
https://codereview.chromium.org/2537413002/ )

Reason for revert:
The problem was resolved.


Original issue's description:
> Revert of wptserve: Enable WPTServe by default. (patchset #1 id:1 of
https://codereview.chromium.org/2497193002/ )
> 
> Reason for revert:
> I suspect that the startup/shutdown logic in wptserve is not right, and we're
seeing intermittent failures where we're hanging trying to start wptserve.
> 
> See crbug.com/669194 and
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Mac10.11/build...
for an example.
> 
> I'm speculatively reverting this for now, to see if things become happier.
> 
> Original issue's description:
> > Reland of wptserve: Enable WPTServe by default.
> 
> TBR=qyearsley@chromium.org,jsbell@chromium.org,tkent@chromium.org
> NOTRY=true
> NOPRESUBMIT=true
> BUG=618366
> 
> Committed: https://crrev.com/b5ce7e0a17e32d6d145124938a90220e9f9990c5
> Cr-Commit-Position: refs/heads/master@{#435129}

TBR=qyearsley@chromium.org,jsbell@chromium.org,dpranke@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=618366
==========

to

==========
Reland of wptserve: Enable WPTServe by default. (patchset #1 id:1 of
https://codereview.chromium.org/2537413002/ )

Reason for revert:
The problem was resolved.


Original issue's description:
> Revert of wptserve: Enable WPTServe by default. (patchset #1 id:1 of
https://codereview.chromium.org/2497193002/ )
> 
> Reason for revert:
> I suspect that the startup/shutdown logic in wptserve is not right, and we're
seeing intermittent failures where we're hanging trying to start wptserve.
> 
> See crbug.com/669194 and
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Mac10.11/build...
for an example.
> 
> I'm speculatively reverting this for now, to see if things become happier.
> 
> Original issue's description:
> > Reland of wptserve: Enable WPTServe by default.
> 
> TBR=qyearsley@chromium.org,jsbell@chromium.org,tkent@chromium.org
> NOTRY=true
> NOPRESUBMIT=true
> BUG=618366
> 
> Committed: https://crrev.com/b5ce7e0a17e32d6d145124938a90220e9f9990c5
> Cr-Commit-Position: refs/heads/master@{#435129}

TBR=qyearsley@chromium.org,jsbell@chromium.org,dpranke@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=618366

Review-Url: https://codereview.chromium.org/2633083002
Cr-Commit-Position: refs/heads/master@{#443953}
Committed:
https://chromium.googlesource.com/chromium/src/+/01c97b5106a69c02931e5aee55e4...
==========

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

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/01c97b5106a69c02931e5aee55e4...

[qyearsley, 2017-01-17 17:01:35]

lgtm