Issue metadata
Sign in to add a comment
|
12.8% regression in thread_times.tough_scrolling_cases at 442950:443071 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8990565510798379408
,
Jan 14 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Bisect Details Configuration: winx64_10_perf_bisect Benchmark : thread_times.tough_scrolling_cases Metric : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame Suspected Commit Range 4 commits in range https://chromium.googlesource.com/chromium/src/+log/38d5cb2144655aad592209bb2a59d21be02df69d..9e81b5fefe756225638bb71dfb097fa11d2a8f8c Revision Result N chromium@442950 12.8111 +- 0.275031 9 good chromium@443011 12.9047 +- 0.977285 14 good chromium@443019 12.7254 +- 0.695169 14 good chromium@443021 --- --- build failure chromium@443023 12.9109 +- 0.425087 21 bad chromium@443026 12.9493 +- 0.461246 14 bad chromium@443041 12.9874 +- 0.229272 6 bad chromium@443071 13.0023 +- 0.183982 6 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --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/8990565510798379408 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6373856962412544 | 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 Tests>AutoBisect. 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 nzolghadr@chromium.org
, Jan 13 2017