From https://bugs.chromium.org/p/chromium/issues/detail?id=670709

In that bug, an autoroller was incorrectly identified as the culprit (due to another bug), and then duped the issue against another issue where the culprit was incorrectly identified as the same autoroller.

We probably shouldn't be blaming autorollers, or at least the known ones for depots we support bisecting.

Maybe if we end up with an autoroller culprit, we should output something to the effect of the culprit was in X depot, but failed to find a culprit with enough confidence.