[14:25] <MacSlow> Greetings everybody!
[20:20] <liushuyu> Hi, can someone help me re-try some autopkgtests? The links follow:
[20:20] <liushuyu> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=meson&trigger=rustc/1.67.1%2Bdfsg0ubuntu1-0ubuntu2
[20:20] <liushuyu> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=s390x&package=meson&trigger=rustc/1.67.1%2Bdfsg0ubuntu1-0ubuntu2
[20:20] <liushuyu> -- end of links. Thank you!
[20:35] <jbicha> liushuyu: no, those tests are always failing, but someone else did a migration-reference/0 test which should allow your package to no longer be blocked by autopkgtest failures there
[20:35] <jbicha> see https://autopkgtest.ubuntu.com/packages/m/meson/lunar/s390x
[20:36] <jbicha> looks like you're good now on those architectures: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#rustc
[20:38] <jbicha> ubuntu-archive: can you ignore meson/blacklisted armhf autopkgtest failures?
[21:01] <vorlon> jbicha: no but you can ask the release team
[21:06] <liushuyu> jbicha: Thank you! Although I think the release team may need to give an explanation on why meson/armhf is blacklisted
[21:07] <bdmurray> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032168
[21:07] -ubottu:#ubuntu-devel- Debian bug 1032168 in src:meson "meson: autopkgtest fills disk completely" [Serious, Open]
[21:08] <bdmurray> liushuyu: ^
[21:08] <liushuyu> bdmurray: Wow. Okay, I guess the tests generated a huge amount of files
[21:10] <bdmurray> liushuyu: there was also a comment (albeit not great) in the never_run file https://git.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-package-configs/commit/?id=76f78dfbef28e07d09b729c006e806b2886722e1
[21:10] -ubottu:#ubuntu-devel- Commit 76f78df in ~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-package-configs "Wow - now meson is an issue on armhf"
[21:12] <liushuyu> bdmurray: Wow - now your commit message is very stylish. Anyways, I can investigate this if you want, I have an arm64 devices at hand (which can run armhf binaries, unlike some newer CPUs)
[21:13] <bdmurray> Well the debian bug report which I only skimmed leads me to believe it is fixed so checking on the status of meson there vs in Ubuntu and removing the never_run entry at an appropriate time would be good next steps.
[21:14] <liushuyu> bdmurray: sounds reasonable