And another one:  https://bugs.chromium.org/p/chromium/issues/detail?id=766559#c5

And another one https://bugs.chromium.org/p/chromium/issues/detail?id=766545#c3

Sullivan as FYI

Some other bisect problems:  

https://bugs.chromium.org/p/chromium/issues/detail?id=766515#c3
https://bugs.chromium.org/p/chromium/issues/detail?id=766532#c3
https://bugs.chromium.org/p/chromium/issues/detail?id=766514#c3
https://bugs.chromium.org/p/chromium/issues/detail?id=766513#c3
https://bugs.chromium.org/p/chromium/issues/detail?id=766531#c3
https://bugs.chromium.org/p/chromium/issues/detail?id=766525#c3

Another one:

https://bugs.chromium.org/p/chromium/issues/detail?id=766516#c3

+Simon

Commented on the first 2, as for all the bugs specified in #c3 they all look like the same root cause. Copy/paste from one of my comments:

This looks like the same problem as  crbug.com/766515 , in that the 2 reference values work but the benchmark is broken for a large portion of the range (and that range is huge). It keeps testing revisions trying to find a working one until eventually it hits the 24 hour limit.

To expand on that comment a bit, since the test is broken in the range, there's not much bisect can do here.