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

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

system_health.common_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

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

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

Perfetto: Add an upper bound to number of events per proto message by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/044129ce84b4e0ea59aaab9398fc9c76b51ae8d2
console:error:all: 0 → 23.4 (+23.4)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

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

Deadline exceeded while waiting for HTTP response from URL: https://monorail-prod.appspot.com/_ah/api/monorail/v1/projects/chromium/issues/907136/comments?alt=json&sendEmail=true