New issue
Advanced search Search tips

Issue 904347 link

Starred by 0 users

Issue metadata

Status: Unconfirmed
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Bisecting fails with not "enough builds to bisect"

Project Member Reported by vabr@chromium.org, Nov 12

Issue description

I just failed to bisect a change in behaviour in recent Chrome versions.
Below is the command I used and the error it printed.


$ python tools/bisect-builds.py -a linux -g 600163 -b 606435 --use-local-cache -- --no-first-run https://accounts.kakao.com
Downloading list of known revisions...
Loaded revisions 15734-382086 from /usr/local/google/home/vabr/chrome/src/tools/.bisect-builds-cache.json
Saved revisions 15734-382086 to /usr/local/google/home/vabr/chrome/src/tools/.bisect-builds-cache.json
Traceback (most recent call last):
  File "tools/bisect-builds.py", line 1242, in <module>
    sys.exit(main())
  File "tools/bisect-builds.py", line 1203, in main
    evaluator, opts.verify_range)
  File "tools/bisect-builds.py", line 800, in Bisect
    raise RuntimeError(msg)
RuntimeError: We don't have enough builds to bisect. revlist: []

 

Sign in to add a comment