Hi, On 05-08-2024 04:25, Jeremy Bícha wrote:
Some Rust autopkgtests take a very long time to complete which is especially noticeable on riscv64 which I think may be the slowest autopkgtest infrastructure.
That's why the test timeout on riscv64 is double that of other architectures: https://salsa.debian.org/ci-team/debian-ci-config/-/blob/master/config/production/nodes.d/riscv64.yaml?ref_type=heads#L11
Some rust autopkgtests have additional trouble because 1. No riscv64 packages are in Testing yet
This is indeed a problem, largely because of 2.
2. The Debian Rust team sets skip-not-installable by default. That means the migration-reference autopkgtest will always show as neutral since the dependencies are uninstallable when migration-reference is the only trigger. I think skip-not-installable by default is bad for other reasons but I think this situation makes it worse.
I regret I added skip-not-installable to autopkgtest. It does more harm than it helps.
See for instance https://ci.debian.net/packages/r/rust-gtk4/testing/riscv64/ which passes once in a while. But I don't believe riscv64 is delaying the rust-zbus transition.
Until yesterday at least rust-libseccomp was blocking a lot. I was hoping that once that migrated (happend yesterday) new tests would have more chance of succes, as it seems that several tests pass in a pure unstable environment. So this hints at missing *versioned* dependencies. But maybe it will resolve itself by time ordering.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
