Issue metadata
Sign in to add a comment
|
21.9%-37.1% regression in v8.browsing_mobile_classic at 466089:466318 |
||||||||||||||||||||
Issue descriptionLooks infra-related - browse_news seems to spike because some sub-stories have stopped producing data.
,
Apr 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981165140815560656
,
Apr 27 2017
,
Apr 29 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : v8.browsing_mobile_classic Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/browse_news 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 v8.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981165140815560656 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4942691084795904 | 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 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980995829616652272
,
Apr 30 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : v8.browsing_mobile_classic Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/browse_news 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 v8.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980995829616652272 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4942691084795904 | 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 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980786702486038368
,
May 3 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : v8.browsing_mobile_classic Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_news 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 v8.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980786702486038368 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4942691084795904 | 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 jgruber@chromium.org
, Apr 27 2017