Another example failure:  http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4288

And another possibly related failure: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1936

Dave, as this week's bug triager, can you take a look? They are all failing in 'Gathering reference values.Recipe failed. Reason: Testing the "good" revision failed' step, but the stdio for that step isn't helpful:

https://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/7016/steps/Gathering%20reference%20values.Recipe%20failed.%20Reason%3A%20Testing%20the%20%22good%22%20revision%20failed/logs/stdio
step returned non-zero exit code: 1
@@@STEP_LOG_LINE@python.inline@import sys; sys.exit(1)@@@
@@@STEP_LOG_END@python.inline@@@
@@@STEP_FAILURE@@@


--------------------------------------------------------------------------------
started: Tue Oct 25 14:22:04 2016
ended: Tue Oct 25 14:22:04 2016
duration: 0 secs
status: FAILURE
status reason: 

https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4288/steps/Gathering%20reference%20values.Recipe%20failed.%20Reason%3A%20Testing%20the%20%22good%22%20revision%20failed/logs/stdio

step returned non-zero exit code: 1
@@@STEP_LOG_LINE@python.inline@import sys; sys.exit(1)@@@
@@@STEP_LOG_END@python.inline@@@
@@@STEP_FAILURE@@@


--------------------------------------------------------------------------------
started: Wed Oct 26 02:48:03 2016
ended: Wed Oct 26 02:48:03 2016
duration: 0 secs
status: FAILURE
status reason: 

Looked at this a little more. In all cases, chartjson from the runs is empty of metrics:

https://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/7016/steps/Gathering%20reference%20values.Reading%20chartjson%20results%20%289%29/logs/json.output
https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4288/steps/Gathering%20reference%20values.Reading%20chartjson%20results%20%286%29/logs/json.output
https://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1936/steps/Gathering%20reference%20values.Reading%20chartjson%20results%20%286%29/logs/json.output

But I can't actually find the stdio from the telememetry test runs that produced no data. Help?

Stephen, can you help out?

Ping - please provide an update to your high priority bug. This bug is stale. Is it really P-1?

We've had a bunch of recent fixes both to bisect and specifically to startup bisect, I think this is obsolete now.

FYI: Underlying cause was most likely crbug.com/677843