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

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


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

android-webview-nexus5X

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

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

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

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14c26259440000

Implement new transform feedback buffer binding rules by jdarpinian@chromium.org
https://chromium.googlesource.com/chromium/src/+/61c71162b81037b9db2b09d03d940b424a5b5eb9

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

It is very difficult to understand what pinpoint is trying to tell me. It looks like it is saying that it did a bunch of builds which failed, and my commit was the only build that succeeded, so it blamed my commit for a regression. I am fairly certain that my commit did not regress image decode performance.

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

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

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

Previous job on this bug failed due to https://github.com/catapult-project/catapult/issues/4393, retrying now that it's fixed.

📍 Pinpoint job started.
https://chromeperf.appspot.com/job/14cf4b3ac40000