Issue metadata
Sign in to add a comment
|
11.3%-16.6% regression in thread_times.key_idle_power_cases at 477543:477635 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977001934044695312
,
Jun 12 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@477542 40.2775 +- 3.60314 21 good chromium@477635 40.0439 +- 4.08495 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/8977001934044695312 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5824297957851136 | 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!
,
Jun 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976989237654036208
,
Jun 13 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@477542 40.9887 +- 5.99481 21 good chromium@477635 40.9984 +- 5.07953 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/8976989237654036208 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5824297957851136 | 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!
,
Jun 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976919665372171456
,
Jun 13 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@476000 40.0521 +- 7.20063 21 good chromium@477800 39.8998 +- 5.80941 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/8976919665372171456 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4960465681121280 | 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!
,
Jun 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976883548247517424
,
Jun 13 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@476000 40.0521 +- 7.20063 21 good chromium@477800 39.8998 +- 5.80941 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/8976883548247517424 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4960465681121280 | 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!
,
Jun 14 2017
The bots are not finding anything. I note there's no ref but I wouldn't be surprised if there had been one if it moved at the same time. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, Jun 12 2017