[Pkg-rust-maintainers] Bug#1144835: rust-inquest: autopkgtest fails under incus-lxc: test failures
Antonio Terceiro
terceiro at debian.org
Wed Aug 19 11:14:40 BST 2026
Source: rust-inquest
Version: 0.3.2-1
Severity: important
Justification: fails autopkgtest on Debian CI infrastructure
Tags: forky sid
User: debian-ci at lists.debian.org
Usertags: lxc
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).
rust-inquest passes its tests under lxc, but fails under incus.
The relevant part of the failure is (hopefully):
> failures:
>
> ---- test_executor::helper_tests::spawn_in_process_group_default_nice_unchanged stdout ----
>
> thread 'test_executor::helper_tests::spawn_in_process_group_default_nice_unchanged' (19379) panicked at src/test_executor.rs:2515:43:
> called `Result::unwrap()` on an `Err` value: ParseIntError { kind: Empty }
> stack backtrace:
> 0: __rustc::rust_begin_unwind
> at /usr/src/rustc-1.95.0/library/std/src/panicking.rs:689:5
> 1: core::panicking::panic_fmt
> at /usr/src/rustc-1.95.0/library/core/src/panicking.rs:80:14
> 2: core::result::unwrap_failed
> at /usr/src/rustc-1.95.0/library/core/src/result.rs:1867:5
> 3: core::result::Result<T,E>::unwrap
> at /usr/src/rustc-1.95.0/library/core/src/result.rs:1233:23
> 4: inquest::test_executor::helper_tests::spawn_in_process_group_default_nice_unchanged
> at ./src/test_executor.rs:2515:43
> 5: inquest::test_executor::helper_tests::spawn_in_process_group_default_nice_unchanged::{{closure}}
> at ./src/test_executor.rs:2506:55
> 6: core::ops::function::FnOnce::call_once
> at /usr/src/rustc-1.95.0/library/core/src/ops/function.rs:250:5
> 7: <fn() -> core::result::Result<(), alloc::string::String> as core::ops::function::FnOnce<()>>::call_once
> at /usr/src/rustc-1.95.0/library/core/src/ops/function.rs:250:5
> note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
>
> ---- test_executor::helper_tests::spawn_in_process_group_applies_nice stdout ----
>
> thread 'test_executor::helper_tests::spawn_in_process_group_applies_nice' (19378) panicked at src/test_executor.rs:2499:33:
> ps output not an integer: ""
> stack backtrace:
> 0: __rustc::rust_begin_unwind
> at /usr/src/rustc-1.95.0/library/std/src/panicking.rs:689:5
> 1: core::panicking::panic_fmt
> at /usr/src/rustc-1.95.0/library/core/src/panicking.rs:80:14
> 2: inquest::test_executor::helper_tests::spawn_in_process_group_applies_nice::{{closure}}
> at ./src/test_executor.rs:2499:33
> 3: core::result::Result<T,E>::unwrap_or_else
> at /usr/src/rustc-1.95.0/library/core/src/result.rs:1622:23
> 4: inquest::test_executor::helper_tests::spawn_in_process_group_applies_nice
> at ./src/test_executor.rs:2499:14
> 5: inquest::test_executor::helper_tests::spawn_in_process_group_applies_nice::{{closure}}
> at ./src/test_executor.rs:2481:45
> 6: core::ops::function::FnOnce::call_once
> at /usr/src/rustc-1.95.0/library/core/src/ops/function.rs:250:5
> 7: <fn() -> core::result::Result<(), alloc::string::String> as core::ops::function::FnOnce<()>>::call_once
> at /usr/src/rustc-1.95.0/library/core/src/ops/function.rs:250:5
> note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
>
>
> failures:
> test_executor::helper_tests::spawn_in_process_group_applies_nice
> test_executor::helper_tests::spawn_in_process_group_default_nice_unchanged
>
> test result: FAILED. 617 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.37s
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, rust-inquest 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/attachments/20260819/cda381ac/attachment-0001.sig>
More information about the Pkg-rust-maintainers
mailing list