Issue metadata
Sign in to add a comment
|
101.8%-202.7% regression in loading.desktop at 494361:495001 |
||||||||||||||||||||
Issue descriptionSplitting of Mac 10.12 regressions from bug 759671 because the root cause of that bug only affects Mac 10.11.
,
Oct 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8966116683177650848
,
Oct 10 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_12_mini_8gb_perf_bisect Benchmark : loading.desktop Metric : cpuTimeToFirstMeaningfulPaint_avg/pcv1-cold/ja.wikipedia Revision Result N chromium@494360 2441.16 +- 2640.59 21 good chromium@494538 2649.08 +- 554.469 20 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=ja.wikipedia loading.desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8966116683177650848 For feedback, file a bug with component Speed>Bisection
,
Oct 10 2017
bisect can't reproduce. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 10 2017