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

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


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

chromium-rel-win7-gpu-nvidia

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/15b267bfc40000

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

Add fieldtrial config for V8CacheInlineScriptCode by leszeks@chromium.org
https://chromium.googlesource.com/chromium/src/+/d955606c25c5ef9cc634cd91c37fb89939600c51

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

This is a warm run, so this is an expected (and, in a sense, good, it means it's working!) regression -- seems that we don't have a hot run to compare it against?

 Issue 844443  has been merged into this issue.

leszeks@: So should we close as WONTFIX given that this was expected?


>  seems that we don't have a hot run to compare it against?
I am not sure if we do. /cc benchmark owners in case they have ideas.

Also, you can see all regressions and improvement coinciding with your CL here:
https://chromeperf.appspot.com/group_report?rev=556806

There may be some interesting improvement and regressions to compare against.

Loading benchmark does not have hot run to compare.

Thanks Majid and Kunihiko, I think the group_report doesn't contain any useful data, and I'm tracking real-world changes through a finch trial anyway: https://uma.googleplex.com/p/chrome/variations?sid=adc0cce8d0de5f08b35705005551aa9f. I'll close as wontfix.