Bisect doesn't find anything - it simply finds all revisions to have the bad value, which ends up marking https://chromium-review.googlesource.com/1226594 as the culprit. That's clearly not right.

In order to bisect in this revision range, I had to checkout catapult to a later revision (582a06eb78355d29316b9d4a2d3181e725194e52) in order to pick up the fix for the issue that broke our perf tests. It's possible that some catapult change is the culprit, in which case not much we can do to bisect.