Issue metadata
Sign in to add a comment
|
27.5% regression in blink_perf.layout at 492161:492227 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971703140967480640
,
Aug 11 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: eb901d2f1051fc2661bf369e390895b9555d9f23 bad_revision : 2440912f23c01e661b47341bb322f50f67cb153b 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@492160 566.963 +- 46.7046 14 good chromium@492194 566.405 +- 43.748 14 good chromium@492211 569.49 +- 60.451 14 good chromium@492215 1061.03 +- 13.3475 6 bad chromium@492219 1056.03 +- 9.26741 6 bad chromium@492227 757.45 +- 850.826 14 bad 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/8971703140967480640 For feedback, file a bug with component Speed>Bisection
,
Sep 18 2017
With more data on the graph, it actually looks like the test is bimodal. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 9 2017