It sounds like this is strictly a Chrome tools problem, but handing to Chrome OS builds for second opinion.  I would guess that bisect-builds.py doesn't work on Chrome OS since it's a Chrome tool, but someone more knowledgeable should say.

Well, it runs from the Linux Chromium OS artifacts from my reading. I don't know who runs that show.

should ask a Chromium tools person since that code lives under chromium/src/tools/.  CrOS doesn't watch anything under that.

maybe check `git log` on the file if no one follows up

/sub

more usefully.. I'm trying to pin down exactly what's available here. Still at early stages of research:

https://docs.google.com/document/d/19IwQUPBKFIhOWyJ5auz8-vy7qUAtVq8-7G2WjAfMIj4/edit


Findings so far are not exactly promising, but the outlook for myself fared better than the description on this issue

For example, this:

  $ ./tools/bisect-builds.py --use-local-cache -a chromeos --good=550428 --bad=561733 --verify-range -- --enable-logging --v=2 --disable-sandbox

_does_ load a window for me. But all renderers immediately crash. I think this hasn't worked since r531204 . Note this is ./tools/bisect-builds.py in the chromium repro.

I'm guessing you're using the (better?) one in https://chrome-internal.googlesource.com/chrome/test/python_tests and yah it doesn't get as far. Downloads but never starts anything, as you say.

woah ok. more unfortunate news.. 

I tried both. I went to the one checked into src/tools after the internal one broke :-/