Issue metadata
Sign in to add a comment
|
12.6%-65.6% regression in v8.mobile_infinite_scroll_tbmv2 at 420100:420133 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 26 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9000441916191624352
,
Sep 26 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@420114 41612381 1163963 18 good chromium@420119 41836555 726691 18 bad Bisect job ran on: android_nexus7_perf_bisect Bug ID: 650292 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.mobile_infinite_scroll_tbmv2 Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_max/discourse Relative Change: 1.10% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3330 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000441916191624352 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5839740408954880 | 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!
,
Sep 30 2016
Graphs have recovered. Closing this bug. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by mythria@chromium.org
, Sep 26 2016