Issue metadata
Sign in to add a comment
|
5.1% regression in memory.top_10_mobile_stress at 419704:419719 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 25 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9000579566165608720
,
Sep 25 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@419703 5679592 91365.6 18 good chromium@419719 5686146 70463.3 18 bad Bisect job ran on: android_one_perf_bisect Bug ID: 649985 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.top_10_mobile_stress Test Metric: memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/http_m_youtube_com_results_q_science Relative Change: 0.87% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1640 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000579566165608720 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5219609207111680 | 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!
,
Oct 3 2016
This does not appear to be a real regression. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by benjhayden@chromium.org
, Sep 25 2016