Report known bisect results at the end of each step.

Report known bisect results at the end of each step. This will allow jobs that fail unexpectedly to be easily resubmitted with a reduced range by perf sheriffs.

Example output:

@@@SEED_STEP Working on [519ed0d5835fc914eb6d320eb7f4e0dbd3c60c8d]@@@
@@@STEP_CURSOR Working on [519ed0d5835fc914eb6d320eb7f4e0dbd3c60c8d]@@@
@@@STEP_STARTED@@@

Working on revision: [519ed0d5835fc914eb6d320eb7f4e0dbd3c60c8d]

Partial results:
         Depot                         Commit SHA                     Mean       Std. Error       State    
        chromium        400664c4101576b48e30da67d57ecffc4d83fcb0      0.00         +-0.00          Bad     
        chromium        fc062604f35d88e607e36ae5f91d19d7cb2251a2      0.00         +-0.00          Bad     
        chromium        1ce4152989e2d33fa10278b4f20267afa70d6be3      0.00         +-0.00          Bad     
        chromium        519ed0d5835fc914eb6d320eb7f4e0dbd3c60c8d      0.00         +-0.00          Bad     

        chromium        481936425a29b2ef6796a1185a8f9008c282b346      0.00         +-0.00          Good    

@@@STEP_CLOSED@@@


BUG=331802
NOTRY=true

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

[tonyg, 2014-01-06 22:44:57]

lgtm

https://codereview.chromium.org/122613004/diff/1/tools/bisect-perf-regression.py
File tools/bisect-perf-regression.py (right):

https://codereview.chromium.org/122613004/diff/1/tools/bisect-perf-regression...
tools/bisect-perf-regression.py:2263: for current_id, current_data in
revision_data_sorted:
Seems like there could be some code reuse here, but up to you.

https://codereview.chromium.org/122613004/diff/1/tools/bisect-perf-regression...
tools/bisect-perf-regression.py:2420: for w in self.warnings:
Nit: Just inline the set() here.

[shatch, 2014-01-06 23:35:48]

https://codereview.chromium.org/122613004/diff/1/tools/bisect-perf-regression.py
File tools/bisect-perf-regression.py (right):

https://codereview.chromium.org/122613004/diff/1/tools/bisect-perf-regression...
tools/bisect-perf-regression.py:2263: for current_id, current_data in
revision_data_sorted:
On 2014/01/06 22:44:57, tonyg wrote:
> Seems like there could be some code reuse here, but up to you.

Folded it all into _PrintTestedCommitsTable.

https://codereview.chromium.org/122613004/diff/1/tools/bisect-perf-regression...
tools/bisect-perf-regression.py:2420: for w in self.warnings:
On 2014/01/06 22:44:57, tonyg wrote:
> Nit: Just inline the set() here.

Done.

[commit-bot: I haz the power, 2014-01-06 23:36:30]

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

[commit-bot: I haz the power, 2014-01-06 23:39:05]

Change committed as 243200