Fix the error message when a new benchmark is added without sharding info

Fix the error message when a new benchmark is added without sharding info

Previously, adding a new benchmark which doesn't have sharding info will
raise a cryptic error message " Device affinity for benchmark ... not found".

This fixes it by telling the user to contact nednguyen@ & martiniss@ for doing the work of scheduling the benchmark.

BUG=chromium:713357
Review-Url: https://codereview.chromium.org/2878483002
Cr-Commit-Position: refs/heads/master@{#470690}
Committed: https://chromium.googlesource.com/chromium/src/+/bc4791b8401ea22c9e8dec630c8c49ad9ffe8b9a

[nednguyen, 2017-05-10 17:50:05]

Description was changed from

==========
Fixing the error message when a new benchmark is added without sharding info
==========

to

==========
Fix the error message when a new benchmark is added without sharding info

Previously, adding a new benchmark which doesn't have sharding info will
raise a cryptic error message " Device affinity for benchmark ... not found".

This fixes it by telling the user to contact nednguyen@ & martiniss@ for doing
the work of scheduling the benchmark.
==========

[nednguyen, 2017-05-10 17:50:05]

nednguyen@google.com changed reviewers:
+ rnephew@chromium.org

[nednguyen, 2017-05-10 17:51:03]

Description was changed from

==========
Fix the error message when a new benchmark is added without sharding info

Previously, adding a new benchmark which doesn't have sharding info will
raise a cryptic error message " Device affinity for benchmark ... not found".

This fixes it by telling the user to contact nednguyen@ & martiniss@ for doing
the work of scheduling the benchmark.
==========

to

==========
Fix the error message when a new benchmark is added without sharding info

Previously, adding a new benchmark which doesn't have sharding info will
raise a cryptic error message " Device affinity for benchmark ... not found".

This fixes it by telling the user to contact nednguyen@ & martiniss@ for doing
the work of scheduling the benchmark.

BUG=chromium:713357
==========

[nednguyen, 2017-05-10 17:51:10]

The CQ bit was checked by nednguyen@google.com to run a CQ dry run

[commit-bot: I haz the power, 2017-05-10 17:52:25]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-10 17:58:33]

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

[commit-bot: I haz the power, 2017-05-10 17:58:33]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[rnephew (Reviews Here), 2017-05-10 18:04:08]

On 2017/05/10 17:50:10, nednguyen wrote:

lgtm

[nednguyen, 2017-05-10 18:31:26]

The CQ bit was checked by nednguyen@google.com

[commit-bot: I haz the power, 2017-05-10 18:33:42]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-10 20:31:19]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1494441086685260, "parent_rev":
"8d7dd373cc6c9168f5e3a22dba0f79418acbe0b6", "commit_rev":
"bc4791b8401ea22c9e8dec630c8c49ad9ffe8b9a"}

[commit-bot: I haz the power, 2017-05-10 20:31:28]

Description was changed from

==========
Fix the error message when a new benchmark is added without sharding info

Previously, adding a new benchmark which doesn't have sharding info will
raise a cryptic error message " Device affinity for benchmark ... not found".

This fixes it by telling the user to contact nednguyen@ & martiniss@ for doing
the work of scheduling the benchmark.

BUG=chromium:713357
==========

to

==========
Fix the error message when a new benchmark is added without sharding info

Previously, adding a new benchmark which doesn't have sharding info will
raise a cryptic error message " Device affinity for benchmark ... not found".

This fixes it by telling the user to contact nednguyen@ & martiniss@ for doing
the work of scheduling the benchmark.

BUG=chromium:713357

Review-Url: https://codereview.chromium.org/2878483002
Cr-Commit-Position: refs/heads/master@{#470690}
Committed:
https://chromium.googlesource.com/chromium/src/+/bc4791b8401ea22c9e8dec630c8c...
==========

[commit-bot: I haz the power, 2017-05-10 20:31:29]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/bc4791b8401ea22c9e8dec630c8c...