Issue metadata
Sign in to add a comment
|
3.4%-4.3% regression in system_health.common_mobile at 551047:551136 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 24 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11f81a49c40000
,
Apr 25 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/11f81a49c40000
,
May 8 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12e370b7c40000
,
May 8 2018
Trying a wider range/different device.
,
May 10 2018
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/12e370b7c40000 [bigint] Allow BigInt(n) for n > MAX_SAFE_INTEGER by jkummerow@chromium.org https://chromium.googlesource.com/v8/v8/+/207bb0371495041f4c144fe8f9a07627d5d0d31a Update V8 to version 6.8.11. by v8-autoroll@chromium.org https://chromium.googlesource.com/chromium/src/+/16d017e2a5ddb80a0fe1b03d68e356e5a6e9171b Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jul 20
The build is broken during the regression. It's a small regression, so WontFix-ing. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Apr 24 2018