Issue metadata
Sign in to add a comment
|
3% regression in speedometer at 507775:507838 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8965605361586357184
,
Oct 17 2017
Please triage.
,
Oct 17 2017
Bisects running. Assigning to perf sheriff.
,
Oct 18 2017
=== BISECT JOB RESULTS === Perf regression found but unable to continue Bisect was stopped because a commit couldn't be classified as either good or bad. Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : speedometer Metric : VanillaJS-TodoMVC/VanillaJS-TodoMVC Revision Result N chromium@507774 1355.39 +- 69.9984 14 good chromium@507781 1366.35 +- 124.303 21 good chromium@507782 --- --- build failure chromium@507783 --- --- build failure chromium@507785 1383.14 +- 135.274 21 unknown chromium@507787 1386.67 +- 98.1502 21 bad chromium@507790 1393.05 +- 87.6029 14 bad chromium@507807 1383.52 +- 79.6978 14 bad chromium@507838 1385.28 +- 117.561 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 speedometer More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8965605361586357184 For feedback, file a bug with component Speed>Bisection
,
Oct 18 2017
Graph recovered. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 16 2017