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

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


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

android-nexus5

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1355ca18440000

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

Turn on AFDO for Chromium on Android by gbiv@chromium.org
https://chromium.googlesource.com/chromium/src/+/274d75742451914f74bbad40c405da7f902dd232

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

Sorry for the noise, gbiv. I was testing a perf dashboard feature by filing a bug on a performance improvement. The bisect in #4 is saying your change to enable AFDO improved the time for a meaningful paint of Flipkart on nexus 5 by ~5%. Great work!

Trust me. I will never complain about a bug filed against me being marked as WontFix before I even get the chance to see it. ;)

Thanks!