Regression in speedometer |
||
Issue descriptionTest: ChromiumPerf/linux-release/speedometer/EmberJS-TodoMVC/Speedometer Value: 1,384.08 (± 33.6073) Point ID: 494891 Time added: 2017-08-17T00:05:24.000Z Chromium Commit Position range: 494600 - 494891 Chromium Git Hash range: cedaac9 - 243f699 V8 Commit Position range: 85bf181 - 4bd66f1
,
Aug 23 2017
=== BISECT JOB RESULTS === NO Perf regression found, tests failed to produce values Bisect Details Configuration: linux_perf_bisect Benchmark : speedometer Metric : EmberJS-TodoMVC/Speedometer Revision Result N chromium@494891 1499.31 +- 148.263 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Speedometer speedometer More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8970450750758184080 For feedback, file a bug with component Speed>Bisection
,
Aug 30 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 23 2017