Issue metadata
Sign in to add a comment
|
44.3%-50.3% regression in v8.browsing_mobile_ignition at 437206:437233 |
||||||||||||||||||||||
Issue descriptionBisecting
,
Dec 12 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8993482764654150816
,
Dec 12 2016
===== BISECT JOB RESULTS =====
Status: failed
=== Bisection aborted ===
The bisect was aborted because Infra Failure: Step('Working on revision chromium@437229,v8@93b87c89f2.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@437205 15818913 5622607 14 good
chromium@437219 16042560 6499678 21 good
chromium@437226 16083281 7816619 21 good
chromium@437228 14837978 2544695 6 good
chromium@437229 16196898 5185439 9 good
chromium@437230 21008220 3915646 6 bad
chromium@437233 19789390 15088557 14 bad
Bisect job ran on: android_one_perf_bisect
Bug ID: 673285
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.nytimes v8.browsing_mobile_ignition
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_avg/browse_news/browse_news_nytimes
Relative Change: 25.10%
Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1871
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993482764654150816
Not what you expected? We'll investigate and get back to you!
https://chromeperf.appspot.com/bad_bisect?try_job_id=5865007470870528
| 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/8993101308769907936
,
Dec 16 2016
===== BISECT JOB RESULTS ===== Status: failed === Bisection aborted === The bisect was aborted because Bisect cannot identify a culprit: Please contact the the team (see below) if you believe this is in error. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@437229 45383269 4589228 21 good chromium@437229,v8@ebe9419228 45525751 4884714 21 unknown chromium@437229,v8@ebb1aff1e6 46759427 7988569 21 bad chromium@437229,v8@93b87c89f2 46857414 5927311 14 bad chromium@437230 46795023 3443589 14 bad Bisect job ran on: android_one_perf_bisect Bug ID: 673285 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.nytimes system_health.memory_mobile Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_news/browse_news_nytimes Relative Change: 3.11% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1879 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993101308769907936 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5862598849855488 | 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 21 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8992648291848667792
,
Dec 21 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2846 Failure reason: the build has failed.
,
Dec 21 2016
,
Dec 23 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8992466667112147664
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982620207283335984
,
Sep 28 2017
Not actionable. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by leszeks@chromium.org
, Dec 12 2016