Issue metadata
Sign in to add a comment
|
54.9%-56.7% regression in thread_times.key_silk_cases at 531515:531543 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 29 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/13f1095a840000
,
Jan 30 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/13f1095a840000
,
Jan 30 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/159236da840000
,
Jan 30 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/159236da840000
,
Feb 5 2018
,
Feb 10 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14e2310d840000
,
Feb 10 2018
Triggered a bisect with a wider range.
,
Feb 11 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14e2310d840000
,
Mar 13 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12b35d76440000
,
Mar 13 2018
Re-running bisect with wider range; it actually failed to produce values in #11.
,
Mar 29 2018
The numbers have recovered since then: https://chromeperf.appspot.com/report?sid=bd4b5edce438c2cf3745b9ba744de200c6db83d88f3233a1f432fb948af9fec4 (thread_raster_cpu_time_per_frame went down to 1.5ms, and thread_GPU_cpu_time_per_frame went back down to 2.0ms). And pinpoint is having issues finding a culprit. So WontFix'ing.
,
Apr 8 2018
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/12b35d76440000
,
Apr 15 2018
Previous job on this bug failed due to https://github.com/catapult-project/catapult/issues/4393, retrying now that it's fixed.
,
Apr 15 2018
📍 Pinpoint job started. https://chromeperf.appspot.com/job/1289cd6ac40000 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jan 29 2018