https://crbug.com/790974 

From drilling down into [0] it seems the root cause is 

'Bisect cannot identify a culprit: Testing the "good" revision failed: Failed to compile revision chromium@519998. Buildbucket job id 8960860087373405024'

1. Couldn't bisection continue at the next revision instead of failing if compilation does not succeed?

2. And is there a way to improve the error message posted on the bug report? In this case it should even be possible to print a list of builds and current results, as is done in other cases. As it stands, I'm not sure how to get the current culprit range, even when manually going into the build logs at [0].

Thanks :)

[0] https://ci.chromium.org/buildbot/tryserver.chromium.perf/android_nexus5X_perf_bisect/2628