Issue metadata
Sign in to add a comment
|
223.2% regression in startup.cold.blank_page at 451993:452087 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 7 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985760699316859536
,
Mar 8 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: winx64_10_perf_bisect Benchmark : startup.cold.blank_page Metric : open_tabs_time/open_tabs_time Change : 117.46% | 227.428571429 -> 494.571428571 Suspected Commit Range 41 commits in range https://chromium.googlesource.com/chromium/src/+log/ec69818af043485daccd4d4f43718390e9ddcb08..e4dd371c464f77b6fbef56d212f7de71e03bf002 Revision Result N chromium@451992 227.429 +- 808.583 21 good chromium@452027 185.5 +- 30.6186 6 good chromium@452028 --- --- build failure --- --- --- too many build failures to list chromium@452067 --- --- build failure chromium@452068 636.667 +- 205.483 6 bad chromium@452087 494.571 +- 1015.88 21 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 startup.cold.blank_page Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8985760699316859536 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5858268997484544 | 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 11 2017
,
Mar 11 2017
,
Mar 11 2017
,
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
, Mar 7 2017