Issue metadata
Sign in to add a comment
|
12.2% regression in v8.key_mobile_sites_smooth at 384299:388858 |
||||||||||||||||||||
Issue descriptionThis test seems to have not been running for three weeks, and hard to say if this is a noise or regression. Recent results are worse than the last run of three weeks ago, but could be a side effect of running with ref, because after the test stopped running, reference results have been improved. I'd run a bisect just in case, though bot could not finish this correctly.
,
Apr 25 2016
failed with "Failed steps failed gathering reference values.performance test 1 of 5 failed gathering reference values.reading chartjson results" twice.
,
Apr 26 2016
kicked another bisect because the blocking issue was fixed
,
Jun 1 2016
,
Oct 6 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999514298570773536
,
Oct 7 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4195 Failure reason: the build has failed due to infrastructure failure.
,
Nov 23 2016
This recovered about a month following the original regression. It's now maybe too far gone to rely on bisect alone and diminished returns.
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982628355708895264
,
Apr 11 2017
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4867 Failure reason: the build has failed due to infrastructure failure. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by toyoshim@chromium.org
, Apr 22 2016