Issue metadata
Sign in to add a comment
|
11.5% regression in speedometer at 484925:485045 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974107040880722304
,
Jul 14 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : speedometer Metric : FlightJS-TodoMVC/FlightJS-TodoMVC Revision Result N chromium@484924 2543.76 +- 443.772 21 good chromium@485045 2562.36 +- 309.319 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/8974107040880722304 For feedback, file a bug with component Speed>Bisection
,
Jul 14 2017
not reproducible |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 14 2017