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

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


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

android-one

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

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

Rename pages in tough_scheduling_cases by amyqiu@google.com
https://chromium.googlesource.com/chromium/src/+/be71236d2c257e74fb599c1ec96fd7e8b116e2c9
No values → 43.75

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

Hmm, I can't figure out how this CL could have caused the regression, since it only renamed the page. Looking at the Pinpoint results, it appears that the test wasn't generating values for the commits up to this CL, could that be related?

@nednguyen, do you have any ideas?

Note that the regression says "No values → 43.75". So I think you may have actually fixed some issue with the benchmark. 

Dave: what is the way to move forward here?

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

amyqiu's change changed the story name. Since Pinpoint uses the story name to look up the results, it couldn't find the results before her change. I re-ran the job with the old story name on the range before her change.

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

Surface Sychronization: Clean-up DelegatedFrameHostAndroid by fsamuel@chromium.org
https://chromium.googlesource.com/chromium/src/+/dba483cee6a5f15e2e2d73df16968ab10b38a2bf
27.45 → 44.12 (+16.67)

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

I believe sadrul@ has fixed this in M69.