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

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


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

Win 7 Nvidia GPU Perf

media.desktop - Benchmark documentation link:
  None

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

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

All of the runs failed. The most common error (20/20 runs) was:
SwarmingTestError: The test failed. No Python exception was found in the log.

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

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

All of the runs failed. The most common error (20/20 runs) was:
SwarmingTestError: The test failed. No Python exception was found in the log.

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

^^ re-running now that blocking bugs are fixed

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

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea
buffering_time: 6.73 → No values

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
buffering_time: No values → 23.93

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

Benchmark documentation link:
  None