ServiceWorker: Update a page set for the test of ServiceWorker

ServiceWorker: Update a page set for the test of ServiceWorker

Currently a wpr file is obsolete, and perf for SW cannot work correctly because of some spec changes. This is solved by this patch.

BUG=372759
TEST=./tools/perf/run_benchmark --browser=android-chrome-shell service_worker.service_worker
This must be executed after commenting out '@benchmark.Disabled' in tools/perf/benchmarks/service_worker.py.

Committed: https://crrev.com/e4f0017af0abc216c66c7252dd53c39fe60693d2
Cr-Commit-Position: refs/heads/master@{#298354}

[shimazu, 2014-10-02 05:43:07]

shimazu@chromium.org changed reviewers:
+ ernstm@chromium.org

[shimazu, 2014-10-02 05:43:07]

Could you review in this patch? :)

[ernstm, 2014-10-03 18:16:41]

On 2014/10/02 05:43:07, makoto wrote:
> Could you review in this patch? :)

service_worker.json still references service_worker_011.wpr, which doesn't exist
anymore. Not sure if this is a problem, but you might want to delete all the
service_worker files in tools/perf/page_sets/data/ and recreate them from
scratch with record_wpr.

[shimazu, 2014-10-06 06:43:12]

On 2014/10/03 18:16:41, ernstm wrote:
> On 2014/10/02 05:43:07, makoto wrote:
> > Could you review in this patch? :)
> 
> service_worker.json still references service_worker_011.wpr, which doesn't
exist
> anymore. Not sure if this is a problem, but you might want to delete all the
> service_worker files in tools/perf/page_sets/data/ and recreate them from
> scratch with record_wpr.

Thanks for your comment!
As you commented, #011 seems to be no longer used, so I recreated the wpr and
json files. 
Then, The number is initialized to #001 and I'm wondering if this will overlap
to #25 currently used. Is this no problem?

[ernstm, 2014-10-06 16:55:59]

On 2014/10/06 06:43:12, makoto wrote:
> On 2014/10/03 18:16:41, ernstm wrote:
> > On 2014/10/02 05:43:07, makoto wrote:
> > > Could you review in this patch? :)
> > 
> > service_worker.json still references service_worker_011.wpr, which doesn't
> exist
> > anymore. Not sure if this is a problem, but you might want to delete all the
> > service_worker files in tools/perf/page_sets/data/ and recreate them from
> > scratch with record_wpr.
> 
> Thanks for your comment!
> As you commented, #011 seems to be no longer used, so I recreated the wpr and
> json files. 
> Then, The number is initialized to #001 and I'm wondering if this will overlap
> to #25 currently used. Is this no problem?

No, this should not be a problem. The new service_worker.json only references
the #001 files. As long as those are in the repository/cloud storage, this
should work fine. LGTM

[shimazu, 2014-10-06 23:14:30]

The CQ bit was checked by shimazu@chromium.org

[commit-bot: I haz the power, 2014-10-06 23:20:07]

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

[commit-bot: I haz the power, 2014-10-06 23:58:11]

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

[commit-bot: I haz the power, 2014-10-06 23:58:12]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[shimazu, 2014-10-07 00:52:50]

The CQ bit was checked by shimazu@chromium.org

[commit-bot: I haz the power, 2014-10-07 00:57:05]

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

[commit-bot: I haz the power, 2014-10-07 03:44:38]

Committed patchset #2 (id:20001) as 2fff5b9f296a9a01779aa7ff49948baec110d251

[commit-bot: I haz the power, 2014-10-07 03:46:04]

Patchset 2 (id:??) landed as
https://crrev.com/e4f0017af0abc216c66c7252dd53c39fe60693d2
Cr-Commit-Position: refs/heads/master@{#298354}