Issue metadata
Sign in to add a comment
|
5.4% regression in v8.browsing_mobile_ignition at 442199:442231 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8990568382447633280
,
Jan 13 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: android_one_perf_bisect Benchmark : v8.browsing_mobile_ignition Metric : memory:chrome:renderer_processes:reported_by_chrome:code_and_metadata_size_max/browse_social/browse_social_twitter Change : 2.00% | 1265262.66667 -> 1290648.0 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/chromium/src/+log/cab7ef9c241ae9e42cea3b6860bf724f5b5d8fca..207f1d8f087c543edfd7d6315f1a472cbae575b8 Revision Result N chromium@442199 1265263 +- 17131.3 9 good chromium@442215 1268647 +- 54595.9 14 good chromium@442220 1265010 +- 35410.4 14 good chromium@442221 1264878 +- 24075.1 9 good chromium@442222 --- --- build failure chromium@442223 1281999 +- 54732.5 14 bad chromium@442231 1290648 +- 55663.2 9 bad To Run This Test 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 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8990568382447633280 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5247957055569920 | 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!
,
Mar 8 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mythria@chromium.org
, Jan 13 2017