Issue metadata
Sign in to add a comment
|
10.1%-66.6% regression in blink_perf.dom at 519768:520369 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8961040609289231568
,
Dec 7 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : blink_perf.dom Metric : move-up-with-hidden-elements/move-up-with-hidden-elements Change : 53.03% | 1.87183333333 -> 2.8645 Revision Result N chromium@519842 1.87183 +- 0.275766 6 good chromium@520202 2.8645 +- 0.694809 6 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.dom More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8961040609289231568 For feedback, file a bug with component Speed>Bisection
,
Jan 22 2018
These all recovered. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 5 2017