Reland of wptserve: Enable WPTServe by default.

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

Reason for revert:
The issue was resolved.  Try to reland without any changes.

Original issue's description:
> Revert of wptserve: Enable WPTServe by default. (patchset #1 id:1 of https://codereview.chromium.org/2482793002/ )
>
> Reason for revert:
>
> I'm reverting this because I think
>
> imported/wpt/html/browsers/history/the-location-interface/reload_post_1.html
>
> started failing with the switch on windows, see
>
> https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7%20%28dbg%29/builds/8056
>
> and I'm the sheriff today.
>
> However, I'm also concerned that I think you missed my comments in #10. I don't think a 30% cycle time regression is okay,
> at least not without an explanation and a plan for addressing it.
>
> Original issue's description:
> > wptserve: Enable WPTServe by default.
> >
> > Feel free to revert this if you see stability issues of imported/wpt tests in
> > webkit_tests step.
> >
> > BUG=618366
> >
> > Committed: https://crrev.com/311d6ccdab758c38b0394a06d054a4db15a5fa21
> > Cr-Commit-Position: refs/heads/master@{#431186}
>
> TBR=qyearsley@chromium.org,jsbell@chromium.org,tkent@chromium.org
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=618366
>
> Committed: https://crrev.com/05bb9406c894324faea17e0b4cc78bcfffafcff4
> Cr-Commit-Position: refs/heads/master@{#431285}

TBR=jsbell@chromium.org,qyearsley@chromium.org,dpranke@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=618366
Committed: https://crrev.com/340ad8ad4eceb6603867b1fc3f9b3b295d76d79d
Cr-Commit-Position: refs/heads/master@{#431820}

[tkent, 2016-11-14 02:14:53]

Created Reland of wptserve: Enable WPTServe by default.

[tkent, 2016-11-14 02:15:11]

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

[commit-bot: I haz the power, 2016-11-14 02:15:26]

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, 2016-11-14 03:08:45]

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

[commit-bot: I haz the power, 2016-11-14 03:08:46]

Dry run: This issue passed the CQ dry run.

[tkent, 2016-11-14 03:13:42]

The CQ bit was checked by tkent@chromium.org

[commit-bot: I haz the power, 2016-11-14 03:13:48]

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-11-14 03:18:11]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-11-14 03:20:14]

Description was changed from

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

Reason for revert:
The issue was resolved.  Try to reland without any changes.


Original issue's description:
> Revert of wptserve: Enable WPTServe by default. (patchset #1 id:1 of
https://codereview.chromium.org/2482793002/ )
> 
> Reason for revert:
> 
> I'm reverting this because I think
> 
> imported/wpt/html/browsers/history/the-location-interface/reload_post_1.html
> 
> started failing with the switch on windows, see
> 
>
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7%20%28dbg%...
> 
> and I'm the sheriff today.
> 
> However, I'm also concerned that I think you missed my comments in #10. I
don't think a 30% cycle time regression is okay,
> at least not without an explanation and a plan for addressing it.
> 
> Original issue's description:
> > wptserve: Enable WPTServe by default.
> >
> > Feel free to revert this if you see stability issues of imported/wpt tests
in
> > webkit_tests step.
> >
> > BUG=618366
> >
> > Committed: https://crrev.com/311d6ccdab758c38b0394a06d054a4db15a5fa21
> > Cr-Commit-Position: refs/heads/master@{#431186}
> 
> TBR=qyearsley@chromium.org,jsbell@chromium.org,tkent@chromium.org
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=618366
> 
> Committed: https://crrev.com/05bb9406c894324faea17e0b4cc78bcfffafcff4
> Cr-Commit-Position: refs/heads/master@{#431285}

TBR=jsbell@chromium.org,qyearsley@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/2495613002/ )

Reason for revert:
The issue was resolved.  Try to reland without any changes.

Original issue's description:
> Revert of wptserve: Enable WPTServe by default. (patchset #1 id:1 of
https://codereview.chromium.org/2482793002/ )
>
> Reason for revert:
>
> I'm reverting this because I think
>
> imported/wpt/html/browsers/history/the-location-interface/reload_post_1.html
>
> started failing with the switch on windows, see
>
>
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win7%20%28dbg%...
>
> and I'm the sheriff today.
>
> However, I'm also concerned that I think you missed my comments in #10. I
don't think a 30% cycle time regression is okay,
> at least not without an explanation and a plan for addressing it.
>
> Original issue's description:
> > wptserve: Enable WPTServe by default.
> >
> > Feel free to revert this if you see stability issues of imported/wpt tests
in
> > webkit_tests step.
> >
> > BUG=618366
> >
> > Committed: https://crrev.com/311d6ccdab758c38b0394a06d054a4db15a5fa21
> > Cr-Commit-Position: refs/heads/master@{#431186}
>
> TBR=qyearsley@chromium.org,jsbell@chromium.org,tkent@chromium.org
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=618366
>
> Committed: https://crrev.com/05bb9406c894324faea17e0b4cc78bcfffafcff4
> Cr-Commit-Position: refs/heads/master@{#431285}

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

Committed: https://crrev.com/340ad8ad4eceb6603867b1fc3f9b3b295d76d79d
Cr-Commit-Position: refs/heads/master@{#431820}
==========

[commit-bot: I haz the power, 2016-11-14 03:20:15]

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

[qyearsley, 2016-11-14 17:33:02]

lgtm

[Dirk Pranke, 2016-11-14 17:33:08]

lgtm

[Dirk Pranke, 2016-11-30 03:19:19]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2537413002/ by dpranke@chromium.org.

The reason for reverting is: 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..