Issue metadata
Sign in to add a comment
|
A zero-to-nonzero to 1.7% regression in page_cycler_v2.intl_ko_th_vi at 462279:462744 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 7 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982930432858729568
,
Apr 8 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : thread_times.simple_mobile_sites Metric : thread_renderer_main_cpu_time_per_frame/thread_renderer_main_cpu_time_per_frame Revision Result N chromium@462290 0.0 +- 0.0 21 good chromium@462744 0.0 +- 0.0 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.simple_mobile_sites Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982930432858729568 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6649516545015808 | 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 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982665406204979104
,
Apr 10 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 : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/background/after_https_m_facebook_com_rihanna 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/8982665406204979104 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5331601401053184 | 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 10 2017
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982619903510664752
,
Apr 11 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 : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/background/after_https_m_facebook_com_rihanna 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/8982619903510664752 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5331601401053184 | 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 12 2017
,
Jun 5 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by m...@chromium.org
, Apr 7 2017