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

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


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

linux-perf
mac-10_13_laptop_high_end-perf

loading.desktop - Benchmark documentation link:
  https://bit.ly/loading-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/163002e2e40000

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

Only flush tokenized chunks to the HTML parser for valid script types. by acomminos@fb.com
https://chromium.googlesource.com/chromium/src/+/174813503285a1ff88efe4fcb8775df6663fa371
timeToFirstContentfulPaint: 78.21 → 187.9 (+109.7)

Plumb build bot status url to perf dashboard data by nednguyen@google.com
https://chromium.googlesource.com/chromium/src/+/043555c46612337596eba9bdec55cc09d7ff0b52
timeToFirstContentfulPaint: 187.9 → 191.3 (+3.478)

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

Benchmark documentation link:
  https://bit.ly/loading-benchmarks

Must be acomminos@fb.com's CL. my CL doesn't affect the test in anyway