Allow adding story keys to values with existing tir labels

Allow adding story keys to values with existing tir labels

Rationale: This is necessary to allow reusing the same story set in both
TBMv1 and TBMv2 benchmarks (e.g.
https://codereview.chromium.org/1907343002/).

BUG=chromium:581716
Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/2f1e6ccff37c899c635e695ca8290925dc0bd429

[petrcermak, 2016-04-22 17:08:32]

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

[petrcermak, 2016-04-22 17:08:32]

PTAL.

Thanks,
Petr

[nednguyen, 2016-04-23 13:17:08]

The CQ bit was checked by nednguyen@google.com

[nednguyen, 2016-04-23 13:17:09]

lgtm

[commit-bot: I haz the power, 2016-04-23 13:17:26]

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

[nednguyen, 2016-04-23 13:18:07]

On 2016/04/23 13:17:09, nednguyen wrote:
> lgtm

Sorry, I forgot about this case of tbm1 benchmarks still exist for a while until
we completely delete them :P

[commit-bot: I haz the power, 2016-04-23 13:32:21]

Description was changed from

==========
Allow adding story keys to values with existing tir labels

Rationale: This is necessary to allow reusing the same story set in both
TBMv1 and TBMv2 benchmarks (e.g.
https://codereview.chromium.org/1907343002/).

BUG=chromium:581716
==========

to

==========
Allow adding story keys to values with existing tir labels

Rationale: This is necessary to allow reusing the same story set in both
TBMv1 and TBMv2 benchmarks (e.g.
https://codereview.chromium.org/1907343002/).

BUG=chromium:581716

Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...
==========

[commit-bot: I haz the power, 2016-04-23 13:32:22]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...