Issue metadata
Sign in to add a comment
|
11.9% regression in blink_perf.parser at 527422:527472 |
||||||||||||||||||||
Issue descriptionThis isn't the clearest regression, so if bisect fails, I'll probably just close this.
,
Jan 9 2018
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8957838643030277504
,
Jan 10 2018
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : blink_perf.parser Metric : query-selector-first/query-selector-first Revision Result N chromium@527421 860.395 +- 35.9786 21 good chromium@527472 855.832 +- 24.4092 21 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.parser More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8957838643030277504 For feedback, file a bug with component Speed>Bisection
,
Jan 25 2018
Looks like this is within the noise. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jan 9 2018