Issue metadata
Sign in to add a comment
|
9.4%-32.5% regression in loading.mobile at 464219:464719 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981888453101278576
,
Apr 20 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : loading.mobile Metric : timeToFirstMeaningfulPaint_avg/Regular-3G/https___m.facebook.com_?soft_messages Revision Result N chromium@464218 7839.94 +- 1038.54 14 good chromium@464719 8622.01 +- 2881.72 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...m.facebook.com..soft.messages loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981888453101278576 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5331785895903232 | 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!
,
Apr 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981797175063432032
,
Apr 20 2017
Simon, looks like this bisect took over 24 hours to run. Is there a narrower range we could re-run?
,
Apr 20 2017
Not that I can see, it couldn't get past the initial gathering revisions, the metric "_avg" is missing from the other runs.
,
Apr 21 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : loading.mobile Metric : timeToFirstMeaningfulPaint_avg/Regular-3G/https___m.facebook.com_?soft_messages Revision Result N chromium@464218 14472.7 +- 230.904 14 good chromium@464719 14298.4 +- 287.42 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...m.facebook.com..soft.messages loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981797175063432032 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5331785895903232 | 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!
,
Apr 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981602559187362304
,
Apr 22 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : loading.mobile Metric : timeToFirstMeaningfulPaint_avg/Regular-3G/http___enquiry.indianrail.gov.in_mntes_MntesServlet?action_MainMenu_subAction_excep_excpType_EC Revision Result N chromium@464709 6863.45 +- 1869.78 21 good chromium@464719 6741.35 +- 446.028 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=http...enquiry.indianrail.gov.in.mntes.MntesServlet.action.MainMenu.subAction.excep.excpType.EC loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981602559187362304 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5331785895903232 | 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!
,
Apr 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980960550390345536
,
Apr 29 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : loading.mobile Metric : timeToFirstMeaningfulPaint_avg/Regular-3G/http___www.slideshare.net Revision Result N chromium@464709 6863.45 +- 1869.78 21 good chromium@464719 6741.35 +- 446.028 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=http...www.slideshare.net loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980960550390345536 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5331785895903232 | 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 27 2017
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, Apr 19 2017