Issue metadata
Sign in to add a comment
|
52.7% regression in page_cycler_v2.intl_ko_th_vi at 421991:422023 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 3 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999809397360810928
,
Oct 3 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/514 Failure reason: the build has failed due to infrastructure failure.
,
Oct 3 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999806486733131280
,
Oct 3 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/516 Failure reason: the build has failed due to infrastructure failure.
,
Oct 4 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999730983471499184
,
Oct 4 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999730975759953232
,
Oct 4 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/521 Failure reason: the build has failed due to infrastructure failure.
,
Oct 5 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/522 Failure reason: the build has failed due to infrastructure failure.
,
Oct 11 2016
This appears to be an increase in noise on one page on one bot, and bisect can't reproduce it. Closing. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, Oct 3 2016