Enable ServiceWorkerMicroBenchmarkPerfTest (service_worker.service_worker_micro_benchmark)

Enable ServiceWorkerMicroBenchmarkPerfTest (service_worker.service_worker_micro_benchmark)

I think https://codereview.chromium.org/884573004/ fixed the ServiceWorker test flakiness.

BUG=442752
TEST=./tools/perf/run_benchmark --browser-executable=~/chromium/src/out/Debug/chrome --also-run-disabled-tests service_worker.service_worker_micro_benchmark

Committed: https://crrev.com/79b35fe9bc28e4e1a2a10ce26edc5d8b46fb362f
Cr-Commit-Position: refs/heads/master@{#317805}

[horo, 2015-02-24 05:50:05]

horo@chromium.org changed reviewers:
+ falken@chromium.org

[horo, 2015-02-24 05:50:06]

falken@
Could you please review?

[falken, 2015-02-24 05:55:50]

On 2015/02/24 05:50:06, horo wrote:
> falken@
> Could you please review?

nice lgtm

[horo, 2015-02-24 06:02:22]

horo@chromium.org changed reviewers:
+ nednguyen@google.com

[horo, 2015-02-24 06:02:22]

nednguyen@
Could you please review this?

Thank you.

[sullivan, 2015-02-24 14:08:55]

sullivan@chromium.org changed reviewers:
+ sullivan@chromium.org

[sullivan, 2015-02-24 14:08:55]

The CQ bit was checked by sullivan@chromium.org

[sullivan, 2015-02-24 14:08:56]

lgtm

I'm going to lgtm+cq this so there is a bit more time for it to cycle through
the bots before perf sheriff comes online.

[commit-bot: I haz the power, 2015-02-24 14:09:35]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/951223002/1

[commit-bot: I haz the power, 2015-02-24 17:05:25]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-24 17:06:13]

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

[Ilya Sherman, 2015-02-24 21:56:32]

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

The reason for reverting is: This immediately re-introduced redness on the tree:

http://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf%20(2)
http://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf%20%282%29/b....

[sullivan, 2015-02-24 21:59:30]

On 2015/02/24 21:56:32, Ilya Sherman wrote:
> A revert of this CL (patchset #1 id:1) has been created in
> https://codereview.chromium.org/943043004/ by mailto:isherman@chromium.org.
> 
> The reason for reverting is: This immediately re-introduced redness on the
tree:
> 
> http://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf%20(2)
>
http://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf%20%282%29/b....

Note: this only broke on reference builds, which are currently M37. Does this
test depend on functionality which is only available in later builds? If so, can
@Disable("reference"), with a comment about which version the reference build
needs to be rolled past to enable. We're currently working on making the
reference build be stable release.

[horo, 2015-02-25 00:01:53]

On 2015/02/24 21:59:30, sullivan wrote:
> On 2015/02/24 21:56:32, Ilya Sherman wrote:
> > A revert of this CL (patchset #1 id:1) has been created in
> > https://codereview.chromium.org/943043004/ by mailto:isherman@chromium.org.
> > 
> > The reason for reverting is: This immediately re-introduced redness on the
> tree:
> > 
> > http://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf%20(2)
> >
>
http://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf%20%282%29/b....
> 
> Note: this only broke on reference builds, which are currently M37. Does this
> test depend on functionality which is only available in later builds? If so,
can
> @Disable("reference"), with a comment about which version the reference build
> needs to be rolled past to enable. We're currently working on making the
> reference build be stable release.

Ah, yes. I forgot about it.
I created a CL "Reenable all except for ref and XP build of
service_worker_micro_benchmark"
https://codereview.chromium.org/951883006/