For http tests, we still need to restrict to --max-locked-shards because otherwise they get flaky waiting on the http server.

For virtual tests, we don't actually want to make them fully parallel in practice because each time we switch to/from a virtual test suite, we need to restart content_shell and that takes forever.

On my machine, I got the following times:
run-webkit-tests --no-retry == 2m56s
run-webkit-tests --no-retry -f == from 6m30s down to 3m15s
run-webkit-tests --no-retry -f --order=random == from 28m (!!) to 2m25s

I have no idea why --order-random is faster, but I tried each one a couple times to be sure and the numbers were very close each time.

Also, -f and --order=random do result in extra flakiness, so they still aren't quite ready for primetime, but this brings it a lot closer.

Review URL: https://codereview.chromium.org/26878008

git-svn-id: svn://svn.chromium.org/blink/trunk@159504 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Expose ServiceWorker via WebRuntimeFeatures

BUG=

Review URL: https://codereview.chromium.org/27069005

git-svn-id: svn://svn.chromium.org/blink/trunk@159505 bbb929c8-8fbe-4397-9dbb-9b2b20218538