> This has always been possible. You can run the tests directly from the > source tree, using previously built .debs: > > autopkgtest --no-built-binaries ../*.deb . -- [...] > > The above works for any virtualization backend.
yes, this worked very well indeed; what i ended up using was (from the (git) source directory): autopkgtest --no-built-binaries /path/to/previously/built/*.deb . -- schroot unstable-amd64-sbuild > If you already have the right binaries installed on your host system and > want to run the tests without any virtualization, it's even simpler: > > autopkgtest -B . -- null > > I have the above aliased as `a`. (-B is the short form for > --no-built-binaries). i dont think this is good enough, as it doesnt isolate from the usually "dirty" development environment of a DD, as i've found out while testing your suggestions: packages that were missing from the binary pkgs Depends were already present on my system and autopkgtests passed, while they fail (correctly) when running them in schroot > We should probably add an examples section to the manpage with this type > of invocations. I'm not sure they belong to the manpage; I gather most of the information i need from the very useful https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.running-tests.rst so maybe that's the right place? or maybe another section/document for "best practices"/"good to know" snippets etc? Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
