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

[Boyuan Yang]

(Please CC me; I am not on the list.)

Hi all,







 74s platform linux -- Python 3.12.6, pytest-8.3.3, pluggy-1.5.0
 74s rootdir: /tmp/autopkgtest-lxc.n_cjis13/downtmp/autopkgtest_tmp/build
 74s configfile: pyproject.toml
 74s plugins: mock-3.14.0, cov-5.0.0, typeguard-4.4.1
 74s collected 0 items
 74s







Thanks,
Boyuan Yang

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. Since this package is not built in autopkgtest, pytest cannot find anything to test and then directly fails: 74s I: pybuild base:311: cd /tmp/autopkgtest-lxc.n_cjis13/downtmp/autopkgtest_tmp/build; python3.12 -m pytest 74s ============================= test session starts ============================== 74s ============================ no tests ran in 0.00s ============================= 74s E: pybuild pybuild:389: test: plugin pyproject failed with: exit code=5: cd /tmp/autopkgtest-lxc.n_cjis13/downtmp/autopkgtest_tmp/build; python3.12 -m pytest 74s pybuild-autopkgtest: error: pybuild --autopkgtest --test-pytest -i python{version} -p 3.12 returned exit code 13 This behavior is different from my understanding of the man page pybuild-autopkgtest(1). Can anyone give me some hints on how to solve this issue (and fix this autopkgtest failure)? [1] https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html

[2] https://tracker.debian.org/pkg/fscacher
[3] https://ci.debian.net/packages/f/fscacher/testing/amd64/54147867/

OpenPGP_signature.asc
Description: OpenPGP digital signature