Issue metadata
Sign in to add a comment
|
23.5%-78.6% regression in thread_times.key_silk_cases at 450439:450551 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987496808466794448
,
Feb 16 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: android_one_perf_bisect Benchmark : thread_times.key_silk_cases Metric : thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame Suspected Commit Range 11 commits in range https://chromium.googlesource.com/chromium/src/+log/140eee5b6a807d78fba47f180340a47d8ebc17ee..2b892c8633d4e17894340683093748d229dcd3e7 Revision Result N chromium@450469 9.65692 +- 0.327104 6 good chromium@450470 --- --- build failure --- --- --- too many build failures to list chromium@450479 --- --- build failure chromium@450480 17.0296 +- 0.764652 6 bad chromium@450490 16.9293 +- 0.259595 6 bad chromium@450510 16.9084 +- 0.362973 6 bad chromium@450551 16.8719 +- 0.261516 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.key_silk_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8987496808466794448 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5785697144799232 | 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
, Feb 16 2017