Issue metadata
Sign in to add a comment
|
3.6%-9% regression in v8.browsing_mobile_ignition at 435594:435707 |
||||||||||||||||||||||||
Issue descriptionBisecting
,
Dec 12 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8993472373417273376
,
Dec 12 2016
===== BISECT JOB RESULTS =====
Status: failed
=== Bisection aborted ===
The bisect was aborted because Infra Failure: Step('Working on revision chromium@435599,v8@a328143eb3.install ChromePublic.apk') returned 2
Please contact the the team (see below) if you believe this is in error.
===== TESTED REVISIONS =====
Revision Mean Std Dev N Good?
chromium@435596 3098457 54213.9 9 good
chromium@435598 3110429 54659.8 6 good
chromium@435599 3115998 50766.4 6 good
chromium@435600 3182049 75971.4 6 bad
chromium@435604 3187177 65159.9 6 bad
chromium@435612 3170500 56165.0 6 bad
chromium@435628 3148195 53395.3 6 bad
Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 673331
Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard v8.browsing_mobile_ignition
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:code_and_metadata_size_avg/browse_news/browse_news_flipboard
Relative Change: 1.61%
Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2323
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993472373417273376
Not what you expected? We'll investigate and get back to you!
https://chromeperf.appspot.com/bad_bisect?try_job_id=5244856606130176
| 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!
,
Dec 12 2016
,
Dec 16 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8993101370860099984
,
Dec 16 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : [regexp] Refactor RegExp.prototype.exec Author : jgruber Commit description: This refactors portions of exec into a new function without RegExpResult construction, which will be used in the future by test, @@match, and @@search fast paths. Unnecessary ToString and ToLength calls as well as repeated map checks were removed. BUG= v8:5339 Review-Url: https://codereview.chromium.org/2540153002 Cr-Commit-Position: refs/heads/master@{#41414} Commit : 65b2ab90ff1cbc90f73568c7ec9d72cb760ac6c8 Date : Thu Dec 01 09:36:08 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@435593 3066369 74508.5 6 good chromium@435597 3084782 59035.2 6 good chromium@435599 3109984 97859.2 9 good chromium@435599,v8@91ea744c74 3101669 33498.2 6 good chromium@435599,v8@65b2ab90ff 3184150 86811.7 6 bad <-- chromium@435599,v8@a328143eb3 3184738 39931.3 6 bad chromium@435600 3203100 50581.0 6 bad chromium@435601 3177359 79493.9 6 bad chromium@435608 3179188 78115.0 6 bad chromium@435622 3184062 37263.3 6 bad chromium@435650 3163539 67352.9 6 bad chromium@435707 3154679 103257 6 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 673331 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard v8.browsing_mobile_ignition Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:code_and_metadata_size_avg/browse_news/browse_news_flipboard Relative Change: 2.88% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2330 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993101370860099984 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5773714635882496 | 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!
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982640103130230992
,
Apr 11 2017
=== BISECT JOB RESULTS ===
Bisect failed unexpectedly
Bisect was aborted with the following:
Infra Failure: Step('Working on revision chromium@435599,v8@a328143eb3.install ChromePublic.apk') returned 2
Bisect Details
Configuration: android_nexus9_perf_bisect
Benchmark : v8.browsing_mobile_ignition
Metric : memory:chrome:renderer_processes:reported_by_chrome:code_and_metadata_size_avg/browse_news/browse_news_flipboard
Revision Result N
chromium@435596 3098457 +- 54213.9 9 good
chromium@435598 3110429 +- 54659.8 6 good
chromium@435599 3115998 +- 50766.4 6 good
chromium@435600 3182049 +- 75971.4 6 bad
chromium@435604 3187177 +- 65159.9 6 bad
chromium@435612 3170500 +- 56165.0 6 bad
chromium@435628 3148195 +- 53395.3 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 --story-filter=browse.news.flipboard v8.browsing_mobile_ignition
Debug Info
https://chromeperf.appspot.com/buildbucket_job_status/8982640103130230992
Is this bisect wrong?
https://chromeperf.appspot.com/bad_bisect?try_job_id=5244856606130176
| 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!
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by leszeks@chromium.org
, Dec 12 2016