Issue metadata
Sign in to add a comment
|
7.3%-12.9% regression in thread_times.key_idle_power_cases at 458495:458948 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983989474120822720
,
Mar 27 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : thread_times.key_idle_power_cases Metric : thread_total_all_cpu_time_per_second/set-timeout.html Revision Result N chromium@458494 41.6011 +- 6.47406 21 good chromium@458948 41.9048 +- 4.99531 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=set.timeout.html thread_times.key_idle_power_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983989474120822720 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5057105175773184 | 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!
,
Mar 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983905521667572560
,
Mar 28 2017
kicked another bisect with a wider range including expected bad results of later revisions
,
Mar 28 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : thread_times.key_idle_power_cases Metric : thread_total_all_cpu_time_per_second/set-timeout.html (Long Idle) Revision Result N chromium@458494 44.709 +- 1.69631 21 good chromium@459006 44.8139 +- 1.91772 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=set.timeout.html..Long.Idle. thread_times.key_idle_power_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983905521667572560 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5265338343620608 | 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!
,
Mar 29 2017
,
Mar 29 2017
,
Mar 29 2017
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982652058025603296
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982632290904953920
,
Apr 11 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : thread_times.key_idle_power_cases Metric : thread_total_all_cpu_time_per_second/set-timeout.html Revision Result N chromium@458494 44.3116 +- 5.68029 21 good chromium@458948 44.6546 +- 4.48156 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=set.timeout.html thread_times.key_idle_power_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982652058025603296 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5057105175773184 | 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! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by toyoshim@chromium.org
, Mar 27 2017