Change port to use apache by default on win7, update test expectations.

Change port to use apache by default on win7, update test expectations.

This switches the default on Win 7 to use the native Win32 version of Apache
2.2 instead of LigHTTPd.  In theory Apache will substantially more stable
and also probably faster. I am hoping that this fixes the situation in bug
378444 where the server just doesn't work on some runs as well.

We also match more of the test expectations on other platforms.

If this change sticks and does improve flakiness, we'll try switching XP
as well in a later change.

This change also deletes all of the FlakyTest entries for http tests
on Win7, so that we can better get a real sense of the flakiness.

R=ojan@chromium.org
BUG=378444, 30536
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=177046

[ojan, 2014-06-14 22:47:21]

lgtm

https://codereview.chromium.org/327423008/diff/1/LayoutTests/FlakyTests
File LayoutTests/FlakyTests (left):

https://codereview.chromium.org/327423008/diff/1/LayoutTests/FlakyTests#oldco...
LayoutTests/FlakyTests:277: Bug(gardener) [ Release Win7 ]
http/tests/appcache/modified-manifest.html [ Pass Timeout ]
I'm not really sure what the benefit of deleting these lines is. It doesn't
affect what gets show in the flakiness dashboard. It just affect whether flaky
failures turn the tree red.

Also, as soon as someone runs update-flaky-tests again, it'll get overwritten.

[Dirk Pranke, 2014-06-14 22:54:06]

On 2014/06/14 22:47:21, ojan wrote:
> lgtm
> 
> https://codereview.chromium.org/327423008/diff/1/LayoutTests/FlakyTests
> File LayoutTests/FlakyTests (left):
> 
>
https://codereview.chromium.org/327423008/diff/1/LayoutTests/FlakyTests#oldco...
> LayoutTests/FlakyTests:277: Bug(gardener) [ Release Win7 ]
> http/tests/appcache/modified-manifest.html [ Pass Timeout ]
> I'm not really sure what the benefit of deleting these lines is. It doesn't
> affect what gets show in the flakiness dashboard. It just affect whether flaky
> failures turn the tree red.

With the lines in the file, we're masking ~10% of the flakiness, and it'll be
hard to really evaluate if things did improve or not.

So for the next couple days, at least, I want to see what happens if no tests
are marked as flaky.

Fortunately, I'm the gardener, so I'm mostly messing w/ myself here.

> Also, as soon as someone runs update-flaky-tests again, it'll get overwritten.

Yeah, I would also like to make sure no one does that for a couple of days,
either.

[Dirk Pranke, 2014-06-14 22:54:29]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2014-06-14 22:55:01]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/dpranke@chromium.org/327423008/1

[Dirk Pranke, 2014-06-14 23:12:12]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2014-06-14 23:13:16]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/dpranke@chromium.org/327423008/20001

[commit-bot: I haz the power, 2014-06-15 00:55:33]

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

[commit-bot: I haz the power, 2014-06-15 00:55:34]

Try jobs failed on following builders:
  win_blink_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/win_blink_rel/builds/12007)

[Dirk Pranke, 2014-06-27 00:22:49]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2014-06-27 00:23:11]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/dpranke@chromium.org/327423008/60001

[commit-bot: I haz the power, 2014-06-27 01:42:20]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  linux_chromium_gn_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/linux_chromium_gn_rel/bu...)

[commit-bot: I haz the power, 2014-06-27 02:36:35]

Change committed as 177046