Issue metadata
Sign in to add a comment
|
1.3% regression in system_health.memory_mobile at 542210:542276 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 13 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12cf800e440000
,
Mar 14 2018
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/12cf800e440000
,
Mar 26 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16c95123440000
,
Apr 8 2018
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/16c95123440000
,
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/12f62f5ac40000
,
May 25 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16e3a232240000
,
May 28 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/16e3a232240000 Don't set active_tree_needs_first_draw_ on invalidate by jamwalla@chromium.org https://chromium.googlesource.com/chromium/src/+/989dd34c86ee3a462c467d0c4200faa9046fa496 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jun 6 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Mar 13 2018