Issue metadata
Sign in to add a comment
|
1.3%-3.1% regression in system_health.memory_desktop at 573164:573172 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 11
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/15b69742a40000
,
Jul 11
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/15b69742a40000 Roll src/third_party/catapult 8a075d7c378a..9eaedb7fa00f (1 commits) by catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com https://chromium.googlesource.com/chromium/src/+/b5896b295b3238c960714f1aef991e022c0a45a0 1.158e+08 → 1.198e+08 (+4.011e+06) Assigning to sheriff sullivan@chromium.org because "Roll src/third_party/catapult 8a075d7c378a..9eaedb7fa00f (1 commits)" is a roll. Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jul 11
Ned: The only CL in the roll is: 2018-07-07 nednguyen@google.com Set non blocking I/O read on ts_proxy subprocess stdout to make sure the timeout Can you take a look to check if this is intended?
,
Jul 11
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 11