Issue metadata
Sign in to add a comment
|
7.8%-56.5% regression in thread_times.simple_mobile_sites at 460502:460619 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983134967286270336
,
Apr 6 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_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame Suspected Commit Range 12 commits in range https://chromium.googlesource.com/chromium/src/+log/1d8ee7b06197fabd1441787a015cdda24e49c838..2f952e4c39887d65126ca4cd67a897fc6d409fb9 Revision Result N chromium@460501 3.71913 +- 0.021875 6 good chromium@460525 3.70097 +- 0.0425415 6 good chromium@460537 3.69725 +- 0.0371421 6 good chromium@460538 --- --- build failure --- --- --- too many build failures to list chromium@460548 --- --- build failure chromium@460549 5.65197 +- 0.138971 6 bad chromium@460596 5.61453 +- 0.144764 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/8983134967286270336 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5253959532412928 | 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 pmeenan@chromium.org
, Apr 5 2017