Issue metadata
Sign in to add a comment
|
3.6%-4.8% regression in thread_times.key_silk_cases at 536813:536935 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 21 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16d5c257840000
,
Feb 22 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/16d5c257840000
,
Feb 23 2018
📍 Pinpoint job started. https://chromeperf.appspot.com/job/11e9381f840000
,
Feb 23 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/11e9381f840000 [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
,
Feb 26 2018
,
Mar 16 2018
+dtu, can you add this to the list of bisects to re-run when we can patch over breakages?
,
May 31 2018
These all recovered. If we need to find the culprit, we can re-run bisect with https://chromium-review.googlesource.com/c/chromium/src/+/922581 pinned. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 21 2018