Re: Testsuite: autopkgtest-pkg-pybuild: weird behavior in my uploaded package

2024-11-08 Thread Roland Mas

Le 08/11/2024 à 08:20, Andrey Rakhmatullin a écrit :

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,


You need to list the files required for testing in 
debian/pybuild.testfiles. Then both dh_auto_test and 
autopkgtest-pkg-pybuild do the right thing.


Roland.



Re: Testsuite: autopkgtest-pkg-pybuild: weird behavior in my uploaded package

2024-11-08 Thread Andrey Rakhmatullin
On Fri, Nov 08, 2024 at 10:03:18AM +0100, Roland Mas wrote:
> You need to list the files required for testing in debian/pybuild.testfiles.
> Then both dh_auto_test and autopkgtest-pkg-pybuild do the right thing.

This is the thing I didn't want to suggest, because dh_auto_test already
works.

-- 
WBR, wRAR


signature.asc
Description: PGP signature