Issue metadata
Sign in to add a comment
|
23.2% regression in v8.browsing_desktop at 521537:521625 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 21 2017
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14a1635e040000
,
Dec 21 2017
๐ Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14a1635e040000
,
Dec 21 2017
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/13f4996e040000
,
Dec 22 2017
๐ Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/13f4996e040000 Replace WTF::Function with base::OnceCallback. By yutak@chromium.org ยท Tue Dec 05 09:39:25 2017 chromium @ d298a4dd732f09c9a1c306a206507c123a3761e2 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Dec 22 2017
The results from pinpoint bot seem bogus; there's no valid metric values observed.
,
Dec 22 2017
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/17c64b4e040000
,
Dec 22 2017
๐ Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/17c64b4e040000
,
Nov 7
This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 21 2017