On Thu, Oct 29, 2020 at 12:14:58PM +0100, Adam Borowski wrote: > On Thu, Oct 29, 2020 at 10:42:21AM +0100, Julian Andres Klode wrote: > > On Thu, Oct 29, 2020 at 02:54:46PM +0900, Ryutaroh Matsumoto wrote: > > > Source: apt > > > Well valgrind is not available on armel, so the test suite > > can't run as it needs valgrind for a test.
Also riscv64, plus a lot of archs I don't care about as much. > > 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. > > 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. It's now in the archive, you can make the autopkgtest b-dep: valgrind-if-available. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Acided and whitepilled. ⠈⠳⣄⠀⠀⠀⠀