Issue metadata
Sign in to add a comment
|
2471.1% regression in memory.top_10_mobile_stress at 447542:447603 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988727074468496208
,
Feb 2 2017
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2431 Failure reason: the build has failed.
,
Feb 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988725391970636384
,
Feb 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988725375072189120
,
Feb 3 2017
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2432 Failure reason: the build has failed due to infrastructure failure.
,
Feb 3 2017
=== BISECT JOB RESULTS === NO Perf regression found, tests failed to produce values Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/background/after_https_www_google_co_uk_hl_en_q_science Revision Result N chromium@447541 2319424 +- 0.0 21 good Please refer to the following doc on diagnosing memory regressions: https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md 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=https.www.google.co.uk.hl.en.q.science memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988725375072189120 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5805623679123456 | 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!
,
Feb 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988659005093456032
,
Feb 3 2017
,
Feb 5 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : waffles Commit : 9fefd20253ceb6af4fc3604ca29fcafc4c8454cd Date : Wed Feb 01 18:56:45 2017 Subject: Update component updater URLs. Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/background/after_https_www_google_co_uk_hl_en_q_science Change : 17.04% | 14586311.1111 -> 17117866.6667 Revision Result N chromium@447560 14586311 +- 344281 9 good chromium@447562 14633643 +- 29913.0 6 good chromium@447563 14630912 +- 20066.2 6 good chromium@447564 17142443 +- 1035736 6 bad <-- chromium@447568 16684373 +- 3841183 9 bad chromium@447575 18099541 +- 18695.6 6 bad chromium@447590 17715200 +- 2117913 6 bad chromium@447620 17117867 +- 2019460 6 bad Please refer to the following doc on diagnosing memory regressions: https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md 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 memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988659005093456032 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6094533781094400 | 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!
,
Mar 11 2017
,
Mar 11 2017
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982620024608775376
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982576319542158016 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jasontiller@chromium.org
, Feb 2 2017