Issue metadata
Sign in to add a comment
|
34.9% regression in blink_perf.layout at 518183:518253 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 24 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8962048099272175488
,
Nov 25 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: 7754b0fbded6c3c0e3329a38d480f1c30e53de8a bad_revision : 15c26a015b0ebea15b0d77ec51a8616f7bc0685b If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : blink_perf.layout Metric : floats_100_100_nested/floats_100_100_nested Revision Result N chromium@518182 579.533 +- 33.3794 14 good chromium@518184 1133.41 +- 9.81687 6 bad chromium@518185 1134.66 +- 12.7555 6 bad chromium@518187 1135.4 +- 14.1095 6 bad chromium@518191 1127.04 +- 11.242 6 bad chromium@518200 1122.88 +- 3.54022 6 bad chromium@518218 775.598 +- 933.892 14 bad chromium@518253 593.618 +- 53.8831 14 bad Please refer to the following doc on diagnosing blink_perf regressions: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.layout More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8962048099272175488 For feedback, file a bug with component Speed>Bisection
,
Jan 22 2018
This metric seems to be bimodal. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 24 2017