Issue metadata
Sign in to add a comment
|
26.2%-27.2% regression in v8.browsing_mobile_ignition at 435133:435153 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 2 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8994367234679538784
,
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@435132 3567682 630831 27 good chromium@435153 3555261 698667 26 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 670752 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.news.washingtonpost v8.browsing_mobile_ignition Test Metric: memory:chrome:renderer_processes:reported_by_chrome:code_and_metadata_size_max/browse_news/browse_news_washingtonpost Relative Change: 0.35% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/940 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994367234679538784 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5304423205568512 | 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 configuration in the nexus5X bots.
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982624088738558816 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mythria@chromium.org
, Dec 2 2016