Issue metadata
Sign in to add a comment
|
3.1% regression in system_health.memory_mobile at 542483:542520 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 14 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/148504de440000
,
Apr 11 2018
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/148504de440000
,
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/14f91f1ac40000
,
May 25 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14c2d42a240000
,
May 30 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14c2d42a240000 Add fieldtrial testing config for new media controls by steimel@chromium.org https://chromium.googlesource.com/chromium/src/+/fdfc5ae4154a67e0539b9d0a77b3c5e2da38f40b 1.186e+08 → 1.218e+08 (+3.164e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 2
,
Aug 2
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Mar 14 2018