Hi, On Mon, Oct 11, 2021 at 09:11:26PM +0200, Andrea Francia wrote:
thank you for your work.
You're welcome.
In order to help I need to be able to reproduce the failures by myself. Can you explain to me how to do it? For example, which command do you use for launching the tests under chroot?
Thank you.
On my local system all the tests pass so the issue is something to do with the build environment, most likely an undeclared package dependency or an environment variable or path assumption that isn't holding. I'm using the tool "sbuild" to initiate the build. This is the same tool as used by Debian's buildds, and works by maintaining a set of chroots to represent a clean unstable install with just the declared build dependencies installed. If you have a Debian system, it's quite easy to set up, see the instructions here: <https://wiki.debian.org/sbuild> Invocation from a clean checkout of that working branch is simply "sbuild". The test phase is invoked via dh_auto_test -O--buildsystem=pybuild This ultimately runs something provided by the "dh-python" package, pybuild, which I am not very familiar with: <https://wiki.debian.org/Python/Pybuild> In turn pybuild appears to try to autodetect the test harness being used and invokes that. It is correctly finding pytest: python3.9 -m pytest tests Eyeballing the failures again quickly now, I think the majority of the failures will be due to not finding the actual test utilities in an expected place in the chroot, variations on: python3: can't open file '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/trash-put': [Errno 2] No such file or directory -- Please do not CC me for listmail. 👱🏻 Jonathan Dowland ✎ j...@debian.org 🔗 https://jmtd.net
