On Thu, Nov 07, 2024 at 08:34:29PM -0500, Boyuan Yang wrote: > According to pybuild-autopkgtest(1) [1], it seems that Python packages that > uses Testsuite: autopkgtest-pkg-build will "run the tests in the same way as > pybuild ... exception that tests are not run in the build directory". I have > some confusion on it with my recent uploads. > > When I look at fscacher/0.4.1-1.1 upload [2], the autopkgtest failure for > this upload is weird. In [3], it looks like the tests are still to be > executed in the "build" directory.
There is no package build directory when autopkgtest runs, because autopkgtest runs in a new separate chroot. That's what the line from the manpage means. > Since this package is not built in autopkgtest, pytest cannot find > anything to test and then directly fails: It's not directly related to building, it's just because your tests are in src/fscacher/tests and so they are not copied into the test dir by default. I don't know what's the preferred best practice for such packages, I imagine both copying the test manually and running tests against /usr/lib/python3/dist-packages/fscacher would work, but I don't think either are possible with autopkgtest-pkg-build, at least if you don't want to do extra copying not needed for build-time tests in d/rules. In my package (python-queuelib) that has a similar layout I haven't switched to autopkgtest-pkg-build. (I would also expect that if a maintainer adds autopkgtests to a package they actually run those before uploading) -- WBR, wRAR
signature.asc
Description: PGP signature
