Hi Clement, On 2025-05-13 16:41, LONGEAC Clement wrote: > Thank you for all your answers ! However I was wondering, is it possible to > do autopkgtest without backend, here (podman+rocm)?
It depends on what you mean. autopkgtest(1) is a testing frontend, and it has many backends of the form autopkgtest-virt-<backend>. The Debian ROCm Team ships an autopkgtest-virt-podman+rocm, which provides the "podman+rocm" backend. So if with "do[ing] autopkgtest without backend", you mean using the autopkgtest(1) *frontend*, then no: a backend is required. If you mean "run the autopkgtest I'm defining in debian/tests/* manually", then you can simply run the test command from that directory, as long as you have the packages installed. > If we don't have a GPU, how do we go about using the backend without a > container? Sorry, I don't quite follow. Without a GPU, you wouldn't run a test at all, right? And a container is just something that some of the autopkgtest-virt-* backends use (be it docker, podman, or lxc). There are other options as well. Schroot is gradually falling into disuse, can we use the unshare backend instead of schroot when ordering autopkgtest? In general: sure, see autopkgtest-virt-unshare(1). However, it won't work with a GPU because there is no way to pass in the GPU device. The backend does have a --bind option, but it only works on directories, not devices. Adding device support looks to be quite easy, I'll file an MR over the weekend. Best, Christian
