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

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


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

android-nexus5x-perf

octane - Benchmark documentation link:
  None

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

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/17f378c9640000

Include testing of significant impacts on a per story basis. by anthonyalridge@google.com
https://chromium.googlesource.com/catapult/+/313f37ed7bc8369d51dbc1d5cb4afcbd48aa5dbb
1.223e+04 → 1.211e+04 (-119.4)

Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) by catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/fcfe9a6f17f02771890c03d666dcebf560eca909
1.211e+04 → 8816 (-3296)

Assigning to sheriff sullivan@chromium.org because "Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits)" is a roll.

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

anthonyalridge: the vast majority of the regression pinpoint caught was due to the catapult roll, which included a change "Limit CPU/GPU frequency for Nexus 5X". That is expected. It also caught a small change from your CL--was it expected to change octane results slightly? Either way, I think it's okay to WontFix, since it's a very small change, but just wanted to send it by you first.

Assigning to mythria since anthonyalridge isn't a project member.

Anthony's cl is related to the new tool we are experimenting with. It should not impact Octane scores. Infact it should not be even used for anything. Since it is minor, I suspect it could be also noise. I think we can mark it as won't fix.