Plumb iteration info

Plumb iteration info

See also catapult-side: https://codereview.chromium.org/2055043002

BUG=catapult:#2405

[benjhayden, 2016-06-09 23:01:39]

Description was changed from

==========
Plumb iteration info

BUG=catapult:#2405
==========

to

==========
Plumb iteration info

See also catapult-side: https://codereview.chromium.org/2055043002

BUG=catapult:#2405
==========

[benjhayden, 2016-06-09 23:07:24]

benjhayden@chromium.org changed reviewers:
+ eakuefner@chromium.org, nednguyen@google.com

[benjhayden, 2016-06-09 23:07:24]

PTAL

[sullivan, 2016-06-10 16:56:56]

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

[sullivan, 2016-06-10 16:56:57]

We need to start by sorting out what goes in the recipe vs telemetry. I feel
like buildbot-specific stuff is better in the recipe, but I could be wrong.
Dave, Ned, opinions?

For background, the current recipe annotates JSON here:
https://cs.chromium.org/chromium/build/scripts/slave/results_dashboard.py?l=181

You'll notice immediately this code is pretty ugly, and later on you'll notice
that the recipes aren't factored well (for what happens on bisect, waterfall,
android, fyi, trybots, etc). Dave has been working on this and will likely have
input.

https://codereview.chromium.org/2055063002/diff/1/tools/perf/core/perf_benchm...
File tools/perf/core/perf_benchmark.py (right):

https://codereview.chromium.org/2055063002/diff/1/tools/perf/core/perf_benchm...
tools/perf/core/perf_benchmark.py:32: info['botName'] = botName
Do we need the bot name? The dashboard automatically pulls it from the test
path.

https://codereview.chromium.org/2055063002/diff/1/tools/perf/core/perf_benchm...
tools/perf/core/perf_benchmark.py:41: 
These are pulled in via the recipe already.