Package: autopkgtest Version: 5.16 Severity: normal X-Debbugs-Cc: mo...@debian.org
Hello, while adding autopkgtests to a package, it seems the only way to iterate over them (adding new tests, fix broken ones) is to fix them in the source package and rebuild it. There are packages that takes hours to build, and that's essentially to write a handful of files in the source package. Is there a better way to incrementally work on autopkgtests that doesnt require to waste hours (sometimes days) just waiting for the source package to build? I think that would greatly improve the developers experience. Thanks, Sandro -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-4-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages autopkgtest depends on: ii apt-utils 2.3.12 ii libdpkg-perl 1.20.9 ii procps 2:3.3.17-5 ii python3 3.9.8-1 ii python3-debian 0.1.39 Versions of packages autopkgtest recommends: ii autodep8 0.24 Versions of packages autopkgtest suggests: ii lxc 1:4.0.10-1 pn lxd <none> pn ovmf <none> pn qemu-efi-aarch64 <none> pn qemu-efi-arm <none> pn qemu-system <none> ii qemu-utils 1:6.1+dfsg-8+b1 ii schroot 1.6.10-12 pn vmdb2 <none> -- no debconf information
