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

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


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

chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12

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

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/111aee92f80000

Trying again using the most significant regression in the bunch.

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

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

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/15d71316f80000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/1482c5a6f80000

Moving to Speed>Bisection. Pinpoint is not reproducing this regression. Graph show uptick across several bots, some pretty severe.

The most significant regression is https://chromeperf.appspot.com/report?sid=17d9b71cbbc938143814dba78ef41b567ed4f24268ca533fc052c59b12166ca2&start_rev=476829&end_rev=514006

The timeAdded is 2017-06-28, so I'm not sure why we got this alert now. We just turned off alerting for the "reported_by_os" memory benchmarks because they were really noisy.

Pinpoint looks broken: all the values are 0 on the graph... It looks like hte tests all failed with the traceback: 

Traceback (most recent call last):
  File "/base/data/home/apps/s~chromeperf/pinpoint:clean-simonhatch-44e40fbe.405031831262280452/dashboard/pinpoint/models/quest/execution.py", line 99, in Poll
    self._Poll()
  File "/base/data/home/apps/s~chromeperf/pinpoint:clean-simonhatch-44e40fbe.405031831262280452/dashboard/pinpoint/models/quest/run_test.py", line 143, in _Poll
    raise SwarmingTestError(self._task_id, result['exit_code'])
SwarmingTestError: The swarming task 39acab8893e00010 failed. The test exited with code 255.

Was this renamed recently?


No benchmark named "media.desktop".

Do you mean any of those benchmarks below?
Available benchmarks are:
  loading.desktop                    A benchmark measuring loading performance of desktop sites. 
  media.android.tough_video_cases   Obtains media metrics for key user scenarios on Android.
  media.media_cns_cases             Obtains media metrics under different network simulations.
  media.mse_cases                   Obtains media metrics for key media source extensions functions.
  media.tough_video_cases           Obtains media metrics for key user scenarios.
  memory.desktop                    Measure memory usage on trivial sites.
  memory.long_running_desktop_sites Measure memory usage on popular sites.
  smoothness.key_desktop_move_cases 
  system_health.common_desktop      Desktop Chrome Energy System Health Benchmark.
  system_health.memory_desktop      Desktop Chrome Memory System Health Benchmark.
  v8.browsing_desktop               
  v8.runtimestats.browsing_desktop  
Pass --browser to list benchmarks for another browser.

yes, it was renamed from media.tough_video_cases_tbmv2 to media.desktop.

Some context, re:comment 10 (timing of alerts seems off) 

- I found these alerts by going to to the AV sheriff dashboard using the link below (normal AFAICT)
- I do not have any buttons pressed to show triaged/improved alerts
- The dashboard started clean this morning, so this alert "arrived" today

(the dashboard link I use)
https://chromeperf.appspot.com/alerts?sortby=end_revision&sortdirection=down&sheriff=Chromium%20Perf%20AV%20Sheriff

Speed infra team: should we file a bug about Chris's seeing really old alerts on our dashboard?

Yeah if an alert suddenly appeared for really old data, that's a bug. I thought there was already a bug tracking that, but I can't find it so file a new one.

Filed https://github.com/catapult-project/catapult/issues/4026