Issue metadata
Sign in to add a comment
|
17.7% regression in thread_times.key_silk_cases at 465235:465372 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981888568757290944
,
Apr 21 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: TIMEOUT The bisect was able to narrow the range, you can try running with: good_revision: 223b9ac0cbebc9029c09318766c8e944af036588 bad_revision : f4ec98a6998d95ab6d81bf5b9a8c1636fdfd874d If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : thread_times.key_silk_cases Metric : thread_renderer_compositor_cpu_time_per_frame/thread_renderer_compositor_cpu_time_per_frame Change : 1.39% | 2.7362611347 -> 2.77423424077 Revision Result N chromium@465234 2.73626 +- 0.03699 6 good chromium@465239 2.77238 +- 0.0515092 9 bad chromium@465243 2.76499 +- 0.0420864 9 bad chromium@465252 2.78896 +- 0.0319037 6 bad chromium@465269 2.78616 +- 0.0351521 6 bad chromium@465303 2.77063 +- 0.0248175 6 bad chromium@465372 2.77423 +- 0.0167497 6 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_silk_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981888568757290944 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6656984633311232 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Apr 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981704965546317712
,
Apr 23 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: 223b9ac0cbebc9029c09318766c8e944af036588 bad_revision : 719ee31460a7948576f62b3d404dc13cfa989f70 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : thread_times.key_silk_cases Metric : thread_renderer_compositor_cpu_time_per_frame/thread_renderer_compositor_cpu_time_per_frame Revision Result N chromium@465234 2.73936 +- 0.0658604 9 good chromium@465237 2.76895 +- 0.0625867 14 bad chromium@465239 2.77335 +- 0.0335215 9 bad chromium@465243 2.77052 +- 0.0442893 9 bad chromium@465252 2.76629 +- 0.0460434 14 bad chromium@465269 2.76657 +- 0.049793 9 bad chromium@465303 2.76612 +- 0.0475167 14 bad chromium@465372 2.7727 +- 0.0255701 9 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_silk_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981704965546317712 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6656984633311232 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Apr 24 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981444792062883936
,
Apr 25 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : thread_times.key_silk_cases Metric : benchmark_duration/benchmark_duration Revision Result N chromium@465215 12.8894 +- 5.3523 21 good chromium@465353 13.1196 +- 6.21289 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_silk_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981444792062883936 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6656984633311232 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
May 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980663175138252736
,
May 3 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : thread_times.key_silk_cases Metric : thread_renderer_compositor_cpu_time_per_frame/thread_renderer_compositor_cpu_time_per_frame Revision Result N chromium@465234 2.76515 +- 0.0787392 21 good chromium@465372 2.77181 +- 0.0722745 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.key_silk_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980663175138252736 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6656984633311232 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jul 27 2017
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, Apr 19 2017