Issue metadata
Sign in to add a comment
|
40.6% regression in loading.desktop at 523105:523185 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 18 2017
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14b795ae040000
,
Dec 18 2017
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14b795ae040000
,
Dec 19 2017
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14be192e040000
,
Dec 19 2017
Restarted with a wider range.
,
Dec 19 2017
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14be192e040000
,
Jan 23 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14eadfe4840000
,
Jan 23 2018
Trying yet another wider range bisect--the test wasn't producing values, but AFAIK pinpoint should at least report a better error now.
,
Jan 23 2018
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/14eadfe4840000
,
Feb 22 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11f6882f840000
,
Feb 22 2018
📍 Found a significant difference after 1 commit. https://chromeperf.appspot.com/job/11f6882f840000 Update RendererSideResourceScheduler testing config by yhirano@chromium.org https://chromium.googlesource.com/chromium/src/+/47b8f2451e900fe2c5fc4d94046925f40fea2fc7 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Feb 22 2018
It's already been reverted. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 18 2017