Issue metadata
Sign in to add a comment
|
2.2%-54% regression in loading.desktop at 493117:493399 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971252481587074096
,
Aug 15 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: daf7d437bb2fd277c9a7bbbfd6ea6e1e5545fe6b bad_revision : 955a7967ee52ade9fd54724a9f798a2fb7477ab3 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: mac_10_12_mini_8gb_perf_bisect Benchmark : loading.desktop Metric : timeToFirstContentfulPaint_avg/pcv1-cold/FDA Revision Result N chromium@493149 826.138 +- 5431.94 21 good chromium@493215 643.106 +- 613.053 14 bad chromium@493280 686.557 +- 907.661 14 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=FDA loading.desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8971252481587074096 For feedback, file a bug with component Speed>Bisection
,
Sep 21 2017
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16b7e3ffb80000
,
Sep 21 2017
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/100a0b2fb80000
,
Sep 21 2017
Doh, bisect failed. Re-kicking on pinpoint.
,
Sep 21 2017
๐ Pinpoint job completed. https://pinpoint-dot-chromeperf.appspot.com/job/16b7e3ffb80000
,
Sep 21 2017
๐ Pinpoint job completed. https://pinpoint-dot-chromeperf.appspot.com/job/100a0b2fb80000 Use swap time for all first paint times in TBM, UMA, UKM & web perf API By shaseley@google.com ยท Thu Aug 10 00:40:36 2017 chromium@c3f876b18c07c50b360b93fb91ec67549b58deb8
,
Sep 21 2017
panicker: assigning to you because this is similar to another issue: shaseley's CL "Use swap time for all first paint times in TBM, UMA, UKM & web perf API" regresses the loading.desktop benchmark (see #8). Should this be WontFix (metrics change)?
,
Sep 21 2017
Yes that is right. It is expected as we updated the metric to capture the cost of more of the rendering pipeline. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 14 2017