Issue metadata
Sign in to add a comment
|
482.7% regression in loading.mobile at 451844:453053 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 7 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985785588655435632
,
Mar 11 2017
,
Jun 21 2017
Issue 699054 has been merged into this issue.
,
Jun 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976203421179204240
,
Jun 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976203396532159744
,
Jun 21 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/Regular-3G/https___guitar-tuner.appspot.com Revision Result N chromium@451843 43213.3 +- 2407.6 21 good chromium@453053 43266.3 +- 2857.87 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 --story-filter=https...guitar.tuner.appspot.com loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976203421179204240 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4936538535755776 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jun 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976188970897410400
,
Jun 21 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/Regular-3G/https___guitar-tuner.appspot.com Revision Result N chromium@451843 43165.2 +- 2982.37 21 good chromium@453053 43301.2 +- 1661.57 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 --story-filter=https...guitar.tuner.appspot.com loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976188970897410400 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4936538535755776 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jun 22 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: 12a3f61803fefb0aeb06f3f4093ea8b06a29fbb3 bad_revision : 250c4a05efdb4ec893d99ed7fe63236686caec4d If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/Regular-3G/https___guitar-tuner.appspot.com Revision Result N chromium@451843 42902.7 +- 2512.63 21 good chromium@452451 42972.4 +- 1717.3 14 good chromium@452770 42841.7 +- 2077.48 14 good chromium@452911 42948.3 +- 1336.05 14 good chromium@452979 43131.4 +- 1135.97 14 good chromium@452980 --- --- build failure --- --- --- too many build failures to list chromium@453053 43406.2 +- 1159.85 14 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 --story-filter=https...guitar.tuner.appspot.com loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976203396532159744 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6155879969193984 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jun 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976109697908806816
,
Jun 22 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/Regular-3G/https___guitar-tuner.appspot.com Revision Result N chromium@451843 43035.3 +- 2246.91 21 good chromium@453053 42966.1 +- 1741.48 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 --story-filter=https...guitar.tuner.appspot.com loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976109697908806816 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6155879969193984 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jul 4 2017
the last good revision shows a bad result in bisects. so this should not be a regression. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by kraynov@chromium.org
, Mar 7 2017