loading.mobile failing on Nexus 5X perf bot |
||||||||
Issue descriptionloading.mobile failing on 3 builders Type: build-failure Builders failed on: - Android Nexus5X Perf (3): https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20Perf%20%283%29 - Android Nexus9 Perf (3): https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus9%20Perf%20%283%29 - Android One Perf (3): https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf%20%283%29
,
Jan 27 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_nexus9_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/timeToFirstContentfulPaint_avg Revision Exit Code N chromium@446318 0 +- N/A 5 good chromium@446368 0 +- N/A 5 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 loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8989365233734631376 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5896647273349120 | 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 Tests>AutoBisect. Thank you!
,
Jan 27 2017
,
Jan 27 2017
,
Jan 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989277815858386144
,
Jan 28 2017
=== BISECT JOB RESULTS === Test failure found but unable to narrow commit range Bisect Details Configuration: android_nexus9_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/timeToFirstContentfulPaint_avg Suspected Commit Range 13 commits in range https://chromium.googlesource.com/chromium/src/+log/36405629cb79a21a8a395592995c62ab39bcf49b..027ca1e1259f228e14ad253169ef0263963122fe Revision Exit Code N chromium@446318 0 +- N/A 5 good chromium@446343 0 +- N/A 5 good chromium@446356 1 +- N/A 5 bad chromium@446368 1 +- N/A 5 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 loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8989277815858386144 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6736048299704320 | 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 Tests>AutoBisect. Thank you!
,
Jan 30 2017
Simon, this looks like a different bisect failure result now. Do you mind taking a look?
,
Jan 30 2017
Hit the 24 hour limit. I'll rekick this with the narrowed range.
,
Jan 30 2017
,
Jan 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989028428336875392
,
Jan 31 2017
=== BISECT JOB RESULTS === Test failure found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: android_nexus9_perf_bisect Benchmark : loading.mobile Metric : timeToFirstMeaningfulPaint_avg/timeToFirstMeaningfulPaint_avg Suspected Commit Range 13 commits in range https://chromium.googlesource.com/chromium/src/+log/36405629cb79a21a8a395592995c62ab39bcf49b..027ca1e1259f228e14ad253169ef0263963122fe Revision Exit Code N chromium@446343 0 +- N/A 5 good chromium@446344 --- --- build failure --- --- --- too many build failures to list chromium@446355 --- --- build failure chromium@446356 1 +- N/A 5 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 loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8989028428336875392 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5849093445779456 | 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 Tests>AutoBisect. Thank you!
,
Mar 31 2017
Nexus 9 bots are gone. The A1 bots seem to have gotten better. The 5X bot seems to have gotten better then broke again recently. Kicking off bisect for it. Renaming to reflect reality.
,
Mar 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983584251656035008
,
Mar 31 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : BenchmarkDuration/BenchmarkDuration Revision Exit Code N chromium@460721 0 +- N/A 4 good chromium@460771 0 +- N/A 4 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=BenchmarkDuration loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983584251656035008 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6722261949612032 | 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!
,
Mar 31 2017
,
Apr 6 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 7
This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jan 26 2017