Issue metadata
Sign in to add a comment
|
No data received for memory.top_10_mobile from android-nexus7v2 since 448299 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 27 2017
,
Mar 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983977585092539680
,
Mar 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983977562771044048
,
Mar 28 2017
=== BISECT JOB RESULTS === NO Perf regression found, tests failed to produce values Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : memory.top_10_mobile 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@448299 5292144 +- 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983977585092539680 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5259483632107520 | 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!
,
Mar 28 2017
,
Mar 29 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/background/after_https_www_google_co_uk_hl_en_q_science Revision Exit Code N chromium@448299 1 +- N/A 20 good chromium@448437 0 +- N/A 20 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 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983977562771044048 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5820604332113920 | 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 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982632372128624336
,
Apr 11 2017
=== BISECT JOB RESULTS === NO Perf regression found, tests failed to produce values Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : memory.top_10_mobile 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@448299 5292144 +- 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982632372128624336 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5259483632107520 | 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 toyoshim@chromium.org
, Mar 27 2017