Ligi wrote this in issue 852685:

"""
Tried bisects with 

1. Per revision bisect-builds.py, received this error.

Command
=======
python bisect_builds.py -o -a win64 -g 565381 -b 566678

Error
=====

Bisecting on continuous Chrome builds. If you would like to bisect on release builds, try running with -r option instead. Previous -o options is currently changed to -r option as continous official builds were added for bisect
Downloading list of known revisions... (use --use-local-cache to cache and re-use the list of revisions)
Total of 0 percent of perf builds available in the range
Traceback (most recent call last):
  File "bisect_builds.py", line 1684, in <module>
    sys.exit(main())
  File "bisect_builds.py", line 1640, in main
    evaluator, opts.verify_range)
  File "bisect_builds.py", line 1044, in Bisect
    raise RuntimeError(msg)
RuntimeError: We don't have enough builds to bisect. revlist: []

2. Wider bisect from -https://www.chromium.org/developers/bisect-builds-py

Here getting all the chromium versions as bad, hence cannot get the exact CL range.

At this point we cannot provide a bisect.
"""

I will investigate a bit.