On Sat, Mar 30, 2024 at 12:28:45PM +0100, Sébastien Jodogne wrote: > Hello, > > On 2/1/24 17:36, Nilesh Patra wrote: > > On Thu, Feb 01, 2024 at 01:55:21PM +0100, Sébastien Jodogne wrote: > > > Even if I'm tagged as the maintainer of "orthanc-python", I don't know > > > how autopkgtest/flaky works (I haven't implemented such tests by > > > myself). > > > > This is the script that runs for tests: > > > > https://salsa.debian.org/med-team/orthanc-python/-/blob/master/debian/tests/run-unit-test?ref_type=heads > > > > This is a basic script that should work and did work at least locally -- note that I only "sponsored" > > an upload for this package and did not delve very deep into the working detaiks. > > Please, I really need help here. Despite hours of trial and error, I'm still > unable to understand how autopkgtest works. Unfortunately, I can't find by > myself a Debian tutorial on how to run such tests. There's a tutorial inside the autopkgtest package itself: $ zcat /usr/share/doc/autopkgtest/README.running-tests.rst.gz > At time point, I build the package using the following command line: > > $ gbp buildpackage -us -uc --git-pristine-tar > --git-export-dir=../build-area/ -j4 > > Once compilation is done, how can I execute autopkgtest? I have tried > multiple variations, including the most basic: > > $ sudo autopkgtest . -- null > $ sudo autopkgtest ../build-area/orthanc-python_4.1+ds-2_amd64.changes -- > null This should work I suppose, in an unstable system. I however pass in the .deb instead of the .changes file. This is the command I use incase that helps you: $ sudo autopkgtest -B ../*.deb -- schroot unstable-amd64-sbuild You could use `-- null` if you don't use a schroot. If this still does not work, can you share the error that you see? > as well as the use of qemu: > > $ sudo autopkgtest-build-qemu unstable /var/tmp/autopkgtest-unstable.img > $ sudo autopkgtest ../build-area/orthanc-python_4.1+ds-2_amd64.changes -- > qemu /var/tmp/autopkgtest-unstable.img > > Could someone indicate me the proper way of calling autopkgtest so that I > can debug the test that was sponsored? I apologize that this upload is creating some un-necessary mess for you 🙁 Best, Nilesh
Attachment:
signature.asc
Description: PGP signature