Issue metadata
Sign in to add a comment
|
2.1%-43.6% regression in system_health.memory_mobile at 405759:405814 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 18 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006785252037871504
,
Jul 18 2016
===== BISECT JOB RESULTS ===== Status: completed === Bisection aborted === The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression. Please contact the the team (see below) if you believe this is in error. === Warnings === The following warnings were raised by the bisect job: * Bisect failed to reproduce the regression with enough confidence. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@405758 21704419 3093011 12 good chromium@405783 22550925 1948216 12 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 629109 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile Test Metric: load_media-memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/load_media_9gag Relative Change: 4.31% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1899 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006785252037871504 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5838990410776576 | 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!
,
Aug 30 2016
,
Aug 30 2016
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by petrcermak@chromium.org
, Jul 18 2016