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

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


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

linux-perf

blink_perf.shadow_dom - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1549b18f640000

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

Use DEFINE_STATIC_LOCAL in CSSProperty::GetPropertyNameAtomicString by fs@opera.com
https://chromium.googlesource.com/chromium/src/+/f7ef1c942101a6560f1d5487a3688d13eaa15be4
9.25 → 9.61 (+0.36)

[layoutng] Store the constraint space as a pointer on LayoutBlock by cbiesinger@chromium.org
https://chromium.googlesource.com/chromium/src/+/f0252116eab5af1a2fba125b1aebbfed08de96b7
9.61 → 10.37 (+0.76)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

That doesn't make sense... this code doesn't run during that test...

This benchmark seems to alternate between fast and slow and in this case it got fast for a day and went back to being slow. I can't see anything in the CLs in either range that looks suspicious. This doesn't seem actionable.