Update SunSpider benchmark from 0.9.1 to 1.0.

Update SunSpider benchmark from 0.9.1 to 1.0.

SunSpider 1.0 results are not comparable to 0.9.1 results. This patch updates
the chromium.perf bots to solely run 1.0 instead of 0.9.1.

BUG=None
TEST=tools/perf/run_multipage_benchmarks --browser=system sunspider tools/perf/page_sets/sunspider.json
NOTRY=True

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=198964

[tonyg, 2013-05-07 22:05:00]

ptal

[bulach, 2013-05-08 08:45:31]

lgtm, but please let danno chime in.

one comment below, feel free to ignore.

https://codereview.chromium.org/14863013/diff/1/chrome/test/data/sunspider/RE...
File chrome/test/data/sunspider/README.chromium (right):

https://codereview.chromium.org/14863013/diff/1/chrome/test/data/sunspider/RE...
chrome/test/data/sunspider/README.chromium:6:
http://trac.webkit.org/browser/trunk/Websites/webkit.org/perf/sunspider-1.0?r...
when I brought in octane, chase told the preferred way was to bring a git
mirror, and just tweak DEPS going forward (specially if there were no
modifications on our side).

the files here are far smaller so probably not worth the effort, but anyways,
just FYI:
https://code.google.com/p/chromium/issues/detail?id=163388

[danno, 2013-05-08 12:18:09]

I can't comment on the mechanics of how to get this into the Chrome testing
framework, but I am 100% for updating to the latest version of SunSpider.

[tonyg, 2013-05-08 19:09:06]

On 2013/05/08 08:45:31, bulach wrote:
> lgtm, but please let danno chime in.
> 
> one comment below, feel free to ignore.
> 
>
https://codereview.chromium.org/14863013/diff/1/chrome/test/data/sunspider/RE...
> File chrome/test/data/sunspider/README.chromium (right):
> 
>
https://codereview.chromium.org/14863013/diff/1/chrome/test/data/sunspider/RE...
> chrome/test/data/sunspider/README.chromium:6:
>
http://trac.webkit.org/browser/trunk/Websites/webkit.org/perf/sunspider-1.0?r...
> when I brought in octane, chase told the preferred way was to bring a git
> mirror, and just tweak DEPS going forward (specially if there were no
> modifications on our side).
> 
> the files here are far smaller so probably not worth the effort, but anyways,
> just FYI:
> https://code.google.com/p/chromium/issues/detail?id=163388

Since it is already checked in this way and the updates are small, I think I'll
just leave it as-is for now.

[commit-bot: I haz the power, 2013-05-08 19:24:29]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tonyg@chromium.org/14863013/29001

[commit-bot: I haz the power, 2013-05-08 19:27:36]

Change committed as 198964