Issue metadata
Sign in to add a comment
|
12.3%-38.6% regression in v8.browsing_mobile_ignition at 435133:435237 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 2 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8994367428865081312
,
Dec 2 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@435182 1262556 229500 27 good chromium@435206 1248838 107874 27 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 670749 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=browse.social.twitter v8.browsing_mobile_ignition Test Metric: memory:chrome:renderer_processes:reported_by_chrome:code_and_metadata_size_avg/browse_social/browse_social_twitter Relative Change: 1.09% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/938 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994367428865081312 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6717681992990720 | 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 21 2016
This was due to a change in bot configuration. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mythria@chromium.org
, Dec 2 2016