Issue metadata
Sign in to add a comment
|
10.2% regression in blink_perf.bindings at 505642:505737 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8966020095860199568
,
Oct 12 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: 75b9c7f5b21199029cddaa14b0e9532ae941f603 bad_revision : 2e63fde900b233194ce1ef52acf160f0b410131e If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : blink_perf.bindings Metric : get-attribute-rare/get-attribute-rare Revision Result N chromium@505641 52.9273 +- 0.389299 6 good chromium@505689 56.8841 +- 0.998666 6 good chromium@505713 57.641 +- 1.87189 6 good chromium@505719 58.2402 +- 0.879698 6 good chromium@505721 45.9616 +- 1.25186 6 bad chromium@505722 45.9973 +- 0.830752 6 bad chromium@505725 45.9335 +- 0.784676 6 bad chromium@505737 48.3355 +- 1.07435 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.bindings More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8966020095860199568 For feedback, file a bug with component Speed>Bisection
,
Dec 12 2017
Bisect unable to find culprit, this regression exists in stable. Ignoring. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 11 2017