#1144844 texinfo: autopkgtest fails under incus-lxc: test-suite FAIL non-zero exit status 2 #1144844
- Package:
- src:texinfo
- Source:
- src:texinfo
- Submitter:
- Antonio Terceiro
- Date:
- 2026-08-20 12:23:02 UTC
- Severity:
- normal
- Tags:
Hi, Debian CI is switching away from lxc containers in favor of incus Containers. This is motivated by security concerns from us; incus is based on lxc, but orchestrates containers substantially different: containers are not privileged (so root in the container is not uid 0 outside of it), and incus imposes a stricter isolation from the host system). texinfo passes its tests under lxc, but fails under incus. The relevant part of the failure is (hopefully): The full autokpgtest logs are available at: https://ci.debian.net/experiments/8/regressions/ (please beware of pagination) Common types of failure and suggested fixes are being documented at: https://wiki.debian.org/ContinuousIntegration/LxcToIncus Note that for the time being, texinfo is still being tested under lxc to avoid disturbing its testing migration test results. If you decide to add the `isolation-machine` restriction to get this package tested under qemu, please mention that explicitly when closing this bug (it's fine to do that only in the package changelog entry that closes the bug) so that we can configure your package for qemu on ci.debian.net.
Hello, Is the salsa CI already running using incus, i.e. can I trigger the fail just by doing another "git push"? Hilmar 19.08.2026 12:23:25 Antonio Terceiro <terceiro@debian.org>:
No. You might want to watch https://salsa.debian.org/salsa-ci-team/pipeline/-/work_items/548 In the meantime the wiki page linked in the bug report has instructions on how to reproduce locally.
Hello, The wiki page states, that a test run is against a pre-built binary. Until now I run my test suite against a source package... Or do you mean, the source package is unpacked in . and the deb files are just pre-built so they don't need to be rebuilt during test run? Hilmar 19.08.2026 19:05:23 Antonio Terceiro <terceiro@debian.org>:
autopkgtest can get both binary and source packages as arguments, as follows: If it gets binaries, it injects those to be installed; if not, the packages to be tested will be downloaded from the archive. The tests to be executed come from the source package, regardless of where the binaries come from. It will build the package by default, unless you pass --no-built-binaries (which ci.debian.net does, because there we want to test the binaries that are in the archive).