Issue metadata
Sign in to add a comment
|
4.1%-27.7% regression in v8.runtimestats.browsing_mobile_classic at 475247:475584 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976807819769750288
,
Jun 15 2017
Assigning to performance sheriff.
,
Jun 16 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: TIMEOUT The bisect was able to narrow the range, you can try running with: good_revision: 515ce76a623d1521ded07bc95f4dde90486b2012 bad_revision : cb9819bdbebd43f5f2a9219dcb127a5368965dcb If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : Optimize:duration_avg/browse_social/browse_social_facebook Change : 20.38% | 456.156125 -> 549.1108 Revision Result N chromium@475246 456.156 +- 56.7168 8 good chromium@475331 445.269 +- 22.7675 5 good chromium@475337 570.482 +- 49.3778 6 bad chromium@475342 573.267 +- 44.17 6 bad chromium@475352 553.341 +- 39.3286 7 bad chromium@475373 573.455 +- 94.5215 7 bad chromium@475415 576.604 +- 45.7976 6 bad chromium@475584 549.111 +- 25.3349 5 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.facebook v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976807819769750288 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5773519029272576 | 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!
,
Jun 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976623075405965280
,
Jun 17 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: 515ce76a623d1521ded07bc95f4dde90486b2012 bad_revision : cb9819bdbebd43f5f2a9219dcb127a5368965dcb If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : Optimize:duration_avg/browse_social/browse_social_facebook Revision Result N chromium@475246 456.156 +- 56.7168 8 good chromium@475331 445.269 +- 22.7675 5 good chromium@475337 570.482 +- 49.3778 6 bad chromium@475342 573.267 +- 44.17 6 bad chromium@475352 553.341 +- 39.3286 7 bad chromium@475373 573.455 +- 94.5215 7 bad chromium@475415 576.604 +- 45.7976 6 bad chromium@475584 549.111 +- 25.3349 5 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.facebook v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976623075405965280 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5773519029272576 | 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!
,
Jun 18 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976454888815694560
,
Jun 19 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_webview_arm64_aosp_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : IC:duration_avg/browse_social/browse_social_facebook Suspected Commit Range 3 commits in range https://chromium.googlesource.com/chromium/src/+log/515ce76a623d1521ded07bc95f4dde90486b2012..2a97a5d29f8b0518066e152d9f87ba5700954796 Revision Result N chromium@475331 765.832 +- 20.0873 12 good chromium@475332 --- --- build failure chromium@475333 --- --- build failure chromium@475334 774.121 +- 40.3891 18 bad chromium@475337 778.745 +- 23.2564 13 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.facebook v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976454888815694560 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4609437802692608 | 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!
,
Jun 26 2017
non-classic cases recovered |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tebbi@chromium.org
, Jun 14 2017