Dear Maintainer, autopkgtest-virt-lxc fails on armel as follows. (I used Raspberry Pi 4B running latest Debian testing). The LXC testbed was made by "debci -s sid -a armel". autopkgtest was run with -u debci -U -B. pkg-config-test FAIL badpkg blame: apt autopkgtest [12:54:35]: @@@@@@@@@@@@@@@@@@@@ summary run-tests FAIL badpkg blame: apt badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. pkg-config-test FAIL badpkg blame: apt badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. Complete log of autopkgtest is attached as zip file. Best regards, Ryutaroh Matsumoto
Sorry I forgot to attach the zipped log. Ryutaroh
Control: retitle -1 apt: test suite dependency valgrind is not available on armel Well valgrind is not available on armel, so the test suite can't run as it needs valgrind for a test. I don't think we have a sane way to express test recommends, so while the test could be skipped if valgrind is not available, I don't see how to make valgrind optional. And I don't really care much for armel, really. But patches welcome, as long as they don't hardcode a list of architectures for valgrind in the test control file.
valgrind-if-available (#928184) is not yet a thing, but that's a problem only for build-time testsuite, not autopkgtests. Meow!
This would skip the entire test suite, which makes it pointless. I'm not gonna run each test case on its own, and there's no difference between tests that always failed or were always skipped, so it's pointless.
Also riscv64, plus a lot of archs I don't care about as much. It's now in the archive, you can make the autopkgtest b-dep: valgrind-if-available. Meow!