Issue metadata
Sign in to add a comment
|
4% regression in thread_times.key_silk_cases at 468626:468735 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980149880036829728
,
May 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980149872428096000
,
May 9 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_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@468625 3.36706 +- 0.111768 21 good chromium@468735 3.34977 +- 0.118968 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 thread_times.key_silk_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980149880036829728 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6373602238136320 | 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 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980080864401572240
,
May 9 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_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@468625 3.38053 +- 0.11237 21 good chromium@468735 3.35887 +- 0.142769 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 thread_times.key_silk_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980149872428096000 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5014843968454656 | 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 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980073316387394032
,
May 10 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_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@468625 3.39617 +- 0.111293 21 good chromium@468735 3.40406 +- 0.130865 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 thread_times.key_silk_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980080864401572240 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6373602238136320 | 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 10 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_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@468625 3.39226 +- 0.140799 21 good chromium@468735 3.37535 +- 0.120559 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 thread_times.key_silk_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980073316387394032 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5014843968454656 | 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 kraynov@chromium.org
, May 8 2017