|10.5%-24593.7% regression in thread_times.key_silk_cases at 534390:534588|
|Project Member Reported by firstname.lastname@example.org, Feb 12||Back to list|
Looks like a return to previous levels after a blip, but will see if bisect finds anything.
All graphs for this bug: https://chromeperf.appspot.com/group_report?bug_id=811321 (For debugging:) Original alerts at time of bug-filing: https://chromeperf.appspot.com/group_report?sid=b176363ead47ec710a28bfe90a756a3f13b081ac14f5b0e750bddb51ba46573b Bot(s) for this bug's original alert(s): android-webview-nexus6
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14dde03d840000
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14dde03d840000
+dtu, simonhatch: can one of you re-kick the bisect when N6 webview is back online?
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1489d13d840000
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1489d13d840000 Revert "Remove browser side GPU info collection on Android." by email@example.com https://chromium.googlesource.com/chromium/src/+/f82bf7763977a48cdb0ebc7afe6a0f07d1593ede Understanding performance regressions: http://g.co/ChromePerformanceRegressions
The CL is a revert. And I relanded again.
|► Sign in to add a comment|