4.1%-53.8% regression in speedometer at 464404:464676 |
|||||||
Issue descriptionSee the link to graphs below.
,
Apr 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982048007361686160
,
Apr 17 2017
,
Apr 17 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: linux_perf_bisect Benchmark : v8.runtimestats.browsing_desktop_classic Metric : Total:duration_avg/browse_media/browse_media_youtube Revision Result N chromium@464556 3217.08 +- 274.271 21 good chromium@464655 3340.14 +- 2359.6 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.youtube v8.runtimestats.browsing_desktop_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982048007361686160 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5892335499476992 | 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!
,
Apr 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982039139929258608
,
Apr 18 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: linux_perf_bisect Benchmark : v8.runtimestats.browsing_desktop_classic Metric : Total:duration_avg/browse_media/browse_media_youtube Change : 16.25% | 3902.4682381 -> 4536.48404762 Suspected Commit Range 15 commits in range https://chromium.googlesource.com/chromium/src/+log/da26a507e1367331f15769f75797fd70032a08b8..d85987aa5fdd5785787516c6b30c3e98844cab3e Revision Result N chromium@464556 3902.47 +- 647.11 21 good chromium@464561 3919.57 +- 295.002 21 good chromium@464562 --- --- build failure --- --- --- too many build failures to list chromium@464575 --- --- build failure chromium@464576 4159.26 +- 2282.47 14 bad chromium@464586 4240.99 +- 2879.74 14 bad chromium@464606 4786.46 +- 4680.01 14 bad chromium@464655 4536.48 +- 4672.43 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.youtube v8.runtimestats.browsing_desktop_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982039139929258608 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5892335499476992 | 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!
,
Apr 19 2017
The only interesting item I can find in the given range is https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/f49ec2dcbd47..30a617a768a1.
,
Apr 19 2017
Issue 712220 has been merged into this issue.
,
Apr 21 2017
This issue is marked as a release blocker with no OS labels associated. Please add an appropriate OS label. All release blocking issues should have OS labels associated to it, so that the issue can tracked and promptly verified, once it gets fixed. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 21 2017
That CL is just a change to the perf dashboard, in an unreleased feature. I'm not sure what to to next here: the build is broken so bisecting on linux is out. I will try bisecting on Mac, but the Mac regression seems to be much noisier and also possibly recovered.
,
Apr 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981692455984108272
,
Apr 21 2017
,
Apr 21 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: mac_pro_perf_bisect Benchmark : v8.runtimestats.browsing_desktop_classic Metric : Total:duration_avg/browse_news/browse_news_nytimes To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.nytimes v8.runtimestats.browsing_desktop_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981692455984108272 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6428693431320576 | 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!
,
Apr 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981689382399208816
,
Apr 21 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: mac_pro_perf_bisect Benchmark : v8.runtimestats.browsing_desktop_classic Metric : Total:duration_avg/browse_news/browse_news_nytimes To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.nytimes v8.runtimestats.browsing_desktop_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981689382399208816 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6428693431320576 | 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!
,
Apr 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981598477767670720
,
Apr 22 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_pro_perf_bisect Benchmark : v8.runtimestats.browsing_desktop_classic Metric : Total:duration_avg/browse_news/browse_news_nytimes Revision Result N chromium@464403 21146.8 +- 4813.12 19 good chromium@464664 21198.4 +- 1605.7 8 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.nytimes v8.runtimestats.browsing_desktop_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981598477767670720 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6428693431320576 | 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!
,
Apr 24 2017
This issue is marked as a release blocker with no OS labels associated. Please add an appropriate OS label. All release blocking issues should have OS labels associated to it, so that the issue can tracked and promptly verified, once it gets fixed. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980947209832413664
,
Apr 29 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : speedometer Metric : VanillaJS-TodoMVC/VanillaJS-TodoMVC Revision Result N chromium@464619 2054.94 +- 108.899 21 good chromium@464666 2051.97 +- 77.8414 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 speedometer Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980947209832413664 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6428693431320576 | 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 8 2017
benhenry@, can we get an owner for this since hablich is OOO? Also, please tag with applicable OSs. Thanks!
,
May 17 2017
,
May 17 2017
If we can't bisect on Linux, we're not going to fix this. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by hablich@chromium.org
, Apr 17 2017