Issue metadata
Sign in to add a comment
|
1.4%-24% regression in system_health.memory_mobile at 434626:434725 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 1 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8994449947653748336
,
Dec 1 2016
===== BISECT JOB RESULTS ===== Status: failed === Bisection aborted === The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence. Please contact the the team (see below) if you believe this is in error. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@434659 79637618 28942983 27 good chromium@434671 76129166 40441787 27 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 670399 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.flickr system_health.memory_mobile Test Metric: memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_media/load_media_flickr Relative Change: None Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4395 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994449947653748336 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5884404113604608 | 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!
,
Dec 13 2016
Closing. Test is noisy and regression level is within the range of earlier results. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by lanwei@chromium.org
, Dec 1 2016