Issue metadata
Sign in to add a comment
|
31.1%-90.7% regression in thread_times.tough_scrolling_cases at 455078:455191 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985639479771425456
,
Mar 9 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: f3dc234c2f85b6262efcf0939c7b0e621a101c91 bad_revision : a11672fb4c998040224d7dc97e5bdc05d46a4145 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : thread_times.tough_scrolling_cases Metric : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame Revision Result N chromium@455077 42.4718 +- 0.298694 6 good chromium@455106 73.1742 +- 5.98752 6 bad chromium@455134 75.5275 +- 4.92509 6 bad chromium@455191 76.4664 +- 10.4059 6 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 thread_times.tough_scrolling_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8985639479771425456 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4986646858039296 | 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 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985597635446810048
,
Mar 9 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: 7615c37d20b7b4a57cf9b4ae7e3034e63003b2ec bad_revision : a11672fb4c998040224d7dc97e5bdc05d46a4145 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : thread_times.tough_scrolling_cases Metric : thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame Revision Result N chromium@455077 5.27147 +- 0.096176 6 good chromium@455092 5.29455 +- 0.098098 6 good chromium@455099 5.30432 +- 0.0642402 6 good chromium@455106 6.62511 +- 0.521916 6 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 thread_times.tough_scrolling_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8985597635446810048 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5626097292541952 | 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 30 2017
This recovered.
,
Apr 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982667409087338336
,
Apr 10 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: f3dc234c2f85b6262efcf0939c7b0e621a101c91 bad_revision : a11672fb4c998040224d7dc97e5bdc05d46a4145 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : thread_times.tough_scrolling_cases Metric : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame Revision Result N chromium@455077 42.4718 +- 0.298694 6 good chromium@455106 73.1742 +- 5.98752 6 bad chromium@455134 75.5275 +- 4.92509 6 bad chromium@455191 76.4664 +- 10.4059 6 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 thread_times.tough_scrolling_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982667409087338336 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4986646858039296 | 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 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982611774602231648
,
Apr 11 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: 7615c37d20b7b4a57cf9b4ae7e3034e63003b2ec bad_revision : a11672fb4c998040224d7dc97e5bdc05d46a4145 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : thread_times.tough_scrolling_cases Metric : thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame Revision Result N chromium@455077 5.27147 +- 0.096176 6 good chromium@455092 5.29455 +- 0.098098 6 good chromium@455099 5.30432 +- 0.0642402 6 good chromium@455106 6.62511 +- 0.521916 6 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 thread_times.tough_scrolling_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982611774602231648 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5626097292541952 | 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 benhenry@google.com
, Mar 9 2017