Issue metadata
Sign in to add a comment
|
11.1%-21.5% regression in smoothness.tough_canvas_cases at 536813:536919 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 21 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11f24a8f840000
,
Feb 21 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/11f24a8f840000
,
Feb 21 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/13e2a9b7840000
,
Feb 23 2018
📍 Found a significant difference after 1 commit. https://chromeperf.appspot.com/job/13e2a9b7840000 [test_env.py] Warm up vpython virtualenv cache on swarming task shards. by iannucci@chromium.org https://chromium.googlesource.com/chromium/src/+/8348d507e280f4bd02a7737bf5577f838d64437e Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Feb 26 2018
,
Mar 16 2018
+dtu can we re-run this after fixing bisect to patch over breakages?
,
May 31 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14c7ea26240000
,
May 31 2018
Re-running bisect with https://chromium-review.googlesource.com/c/catapult/+/1077070 pinned.
,
May 31 2018
,
May 31 2018
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/14c7ea26240000 All of the attempts failed. See the individual attempts for details on each error.
,
May 31 2018
Looks like that wasn't the right patch. But even if it was, you'd run into the same issue as https://bugs.chromium.org/p/chromium/issues/detail?id=810022#c23
,
Oct 18
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 21 2018