Issue metadata
Sign in to add a comment
|
28% regression in blink_perf.layout at 504407:504463 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8966725662817953632
,
Oct 5 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: 5b51043c7c8e7e6b86e68e6d93d95ad24e11cf0e bad_revision : c690a9aad92aea61ea5c72e0f603aadf95663899 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 : large-table-with-collapsed-borders-and-colspans/large-table-with-collapsed-borders-and-colspans Revision Result N chromium@504406 2467.74 +- 42.8383 14 good chromium@504408 4310.77 +- 53.1855 6 bad chromium@504410 4318.92 +- 41.0381 6 bad chromium@504414 4300.02 +- 21.3849 6 bad chromium@504421 2510.86 +- 13.325 6 bad chromium@504435 2493.23 +- 24.9582 6 bad chromium@504463 2482.3 +- 32.8189 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/8966725662817953632 For feedback, file a bug with component Speed>Bisection
,
Oct 13 2017
Wontfix. that graph seem to have just bursts of noise |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 3 2017