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

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


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

chromium-rel-mac11-pro

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

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

📍 Pinpoint job started.
https://chromeperf.appspot.com/job/128a96df840000

📍 Couldn't reproduce a difference.
https://chromeperf.appspot.com/job/128a96df840000

Hey Annie here's another strange one.  The graph suggests a big improvement in this metric, yet the bots can't find out what caused it.

+Dave, Simon:

Actually the reporting here isn't great, I think this is https://github.com/catapult-project/catapult/issues/4231. Dave, Simon, I thought this was on the backlog for this week but now I don't see it there, any update? This is pretty confusing for perf sheriffs.

Alex, looks like the test is actually not producing any values for FarsNews, so pinpoint is saying 0=0->no repro. (Don't worry, we're still following up on these). In this case, we actually took down the Mac 11 bots recently as less than 20% of our mac users are on 10.11 and this is dropping. It doesn't repro on Mac 10.12: https://chromeperf.appspot.com/report?sid=a4877520ca1a9cf1075e89d8838dd4bfa2596a4fa019daf67abc131ba08214a0&rev=534268

So since the test isn't spitting out values, and this config doesn't represent much of the population, WontFix-ing.

Originally it was, but with all the failures around vpython and bisects thought it might be better to prioritize having Pinpoint know how to patch in fixes in broken ranges. I think next week is still up in the air, so bumping this back up shouldn't be an issue.