All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=814199

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=bdf596be48e97c65621e5640509d78c164b9dc06c15babeeb5b4a1f62beb335c


Bot(s) for this bug's original alert(s):

android-one

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14852517840000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14852517840000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16102307840000

📍 Found a significant difference after 1 commit.
https://chromeperf.appspot.com/job/16102307840000

[test_env.py] Warm up vpython virtualenv cache on swarming task shards. by iannucci@chromium.org
https://chromium.googlesource.com/chromium/src/+/8348d507e280f4bd02a7737bf5577f838d64437e

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

+dtu, can you add this to the list of bisects to re-run when we can patch over breakages?

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14a33a26240000

Re-running bisect with fix https://chromium-review.googlesource.com/c/catapult/+/1077070 pinned and on a wider range.

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14a33a26240000

All of the attempts failed. See the individual attempts for details on each error.

Looks like that wasn't the right patch. But even if it was, you'd run into the same issue as https://bugs.chromium.org/p/chromium/issues/detail?id=810022#c23

Available, but no owner or component? Please find a component, as no one will ever find this without one.