Update Browsermark benchmark to specify a bucket in it's pageset.

Update Browsermark benchmark to specify a bucket in it's pageset.

BUG=435174
Committed: https://crrev.com/6e387ed08adbf8b1f823e55ff9f9f0f9fe9a97d4
Cr-Commit-Position: refs/heads/master@{#305079}

[aiolos (Not reviewing), 2014-11-20 18:08:16]

aiolos@chromium.org changed reviewers:
+ dtu@chromium.org, tonyg@chromium.org

[tonyg, 2014-11-20 18:30:08]

lgtm

I assume something is in the works to automatically enforce that these are all
correct once we fix them all up?

[aiolos (Not reviewing), 2014-11-20 19:07:14]

On 2014/11/20 18:30:08, tonyg wrote:
> lgtm
> 
> I assume something is in the works to automatically enforce that these are all
> correct once we fix them all up?

Yes, this is my goal for this fixit: People shouldn't be able to accidentally
upload the benchmarks to the wrong bucket. And if they upload it to the wrong
bucket on purpose (using gsutil or cloud_storage), it should fail in an
understandable way. And there should be good documentation on what to do if a
PageSet needs to be moved to a different bucket. (For example: if a
google-internal site is added or removed from the PageSet.)

[aiolos (Not reviewing), 2014-11-20 19:07:19]

The CQ bit was checked by aiolos@chromium.org

[commit-bot: I haz the power, 2014-11-20 19:08:17]

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

[commit-bot: I haz the power, 2014-11-20 21:19:46]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-11-20 21:20:30]

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