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

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


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

chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac12
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win8-dual
linux-release

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14a5bec8240000

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

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

All of the attempts failed. See the individual attempts for details on each error.

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

[parser] Skipping inner funcs: Turn flag back on. by marja@chromium.org
https://chromium.googlesource.com/v8/v8/+/fa3b73fffe232b601d2a94f129446f41c765a86e

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

Oh, this old one is popping up again?

This bug is about the background parsing time going up, but based on our analysis back then, the total parse time still goes down.

Oh, I am sorry, I had some old bugs that I am trying to triage and pinpoint helpfully assigns to people :-/