[telemetry] Upload results to cloud storage.

[telemetry] Add an option --upload-results to store the html results in google storage. Would like to be able to use this from the perf try bot to store the html results of each submitted job.


BUG=

TEST=tools/perf/run_measurement -v --browser=release blink_perf third_party/WebKit/PerformanceTests/Bindings/typed-array-construct-from-typed.html --upload-results


Example output:

View online at http://storage.googleapis.com/chromium-telemetry/html-results/results-2013-10-15_16-05-23

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

[dtu, 2013-10-15 21:49:53]

https://codereview.chromium.org/27413002/diff/1/tools/telemetry/telemetry/pag...
File tools/telemetry/telemetry/page/html_page_measurement_results.py (right):

https://codereview.chromium.org/27413002/diff/1/tools/telemetry/telemetry/pag...
tools/telemetry/telemetry/page/html_page_measurement_results.py:112:
cloud_storage.Insert(cloud_storage.PUBLIC_BUCKET, file_hash, file_path)
We're creating a new bucket for these, right? Also, are we sticking with the
hash, or giving them human-readable names?

[shatch, 2013-10-15 21:59:37]

https://codereview.chromium.org/27413002/diff/1/tools/telemetry/telemetry/pag...
File tools/telemetry/telemetry/page/html_page_measurement_results.py (right):

https://codereview.chromium.org/27413002/diff/1/tools/telemetry/telemetry/pag...
tools/telemetry/telemetry/page/html_page_measurement_results.py:112:
cloud_storage.Insert(cloud_storage.PUBLIC_BUCKET, file_hash, file_path)
On 2013/10/15 21:49:53, dtu wrote:
> We're creating a new bucket for these, right? Also, are we sticking with the
> hash, or giving them human-readable names?

Yeah I could create a new bucket. Is it possible to create a sub directory under
chromium-telemetry, ie. chromium-telemetry/results?

I don't have a strong opinion about hash vs name, could maybe assemble one from
parameters/time? wdyt?

[shatch, 2013-10-15 23:11:53]

New snapshot uploaded.

From discussion offline, uploaded the results to a directory html-results under
chromium-telemetry, and also created a unique result name from time.

[dtu, 2013-10-16 01:30:03]

lgtm

[commit-bot: I haz the power, 2013-10-17 21:06:26]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/simonhatch@chromium.org/27413002/22001

[commit-bot: I haz the power, 2013-10-17 23:16:50]

Step "update" is always a major failure.
Look at the try server FAQ for more details.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2013-10-17 23:23:37]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/simonhatch@chromium.org/27413002/41001

[commit-bot: I haz the power, 2013-10-18 01:42:27]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/simonhatch@chromium.org/27413002/41001

[commit-bot: I haz the power, 2013-10-18 19:42:31]

Retried try job too often on win7_aura for step(s) browser_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win7_aura&...

[commit-bot: I haz the power, 2013-10-18 21:34:58]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/simonhatch@chromium.org/27413002/41001

[commit-bot: I haz the power, 2013-10-19 10:36:34]

Retried try job too often on win7_aura for step(s) app_list_unittests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win7_aura&...

[commit-bot: I haz the power, 2013-10-19 15:21:06]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/simonhatch@chromium.org/27413002/41001

[commit-bot: I haz the power, 2013-10-19 18:36:00]

Change committed as 229612