UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36

Steps to reproduce the problem:
I would like to be able to use the bisect script to run a specific version of Chrome. I can do something similar in Firefox's bisect script. In Chrome's however I get an error not enough to bisect.

What is the expected behavior?
I think there should be an option like --run-build 234 or something so it would just automatically download and cache it and run it

What went wrong?
python chrome-bisect-builds.py -a win -g 414596 -b 414596 --use-loca
l-cache --verify-range -- --no-first-run  --user-data-dir=/temp --force-device-s
cale-factor=1
Downloading list of known revisions...
Loaded revisions 1625-425547 from X:\ffupdate\.bisect-builds-cache.json
Traceback (most recent call last):
  File "chrome-bisect-builds.py", line 1174, in <module>
    sys.exit(main())
  File "chrome-bisect-builds.py", line 1135, in main
    evaluator, opts.verify_range)
  File "chrome-bisect-builds.py", line 742, in Bisect
    raise RuntimeError(msg)
RuntimeError: We don't have enough builds to bisect. revlist: [414596]

Did this work before? N/A 

Chrome version: 55.0.2883.75  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0