Issue metadata
Sign in to add a comment
|
4% regression in speedometer at 516305:516385 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8962786222162010528
,
Nov 16 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : speedometer Metric : EmberJS-TodoMVC/EmberJS-TodoMVC Revision Result N chromium@516304 7062.36 +- 531.004 21 good chromium@516385 7062.36 +- 396.362 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --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/8962786222162010528 For feedback, file a bug with component Speed>Bisection
,
Nov 16 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 16 2017