Hi, the code is very simple, and the failure seems not to be qemu but busybox. At a high level it seems a feature is missing on riscv?
If you look at: https://git.launchpad.net/ubuntu/+source/qemu/tree/debian/tests/test-qemu-user.sh?h=ubuntu/questing-devel#n33 it is weird. the busybox is from the target release each time. If the host is e.g. amd64 it works to emulate arm64 and run it's busybox But if the host is riscv64 it fails to emulate arm64 and run it's busybox ... 2662s glob with sh: /usr/bin/qemu-arm64 /bin/busybox ash -c "/usr/bin/qemu-arm64 /bin/busybox ls -dCFl debian/*[t]*": 2663s : applet not found ... This is clearly a busybox error, but triggering depending on having a certin host or not that is emulating it ?!? That is odd at least, can we somehow try to simplify the testcase here. I mean, that should be just "these few commands on riscv fail, same on other platform work" And then report it to upstream or if there is some insight go down that debugging path. For example - could we have - amd64 vs riscv64 host - ensure all used versions are the same - installing arm64 busybox - running /usr/bin/qemu-arm64 /bin/busybox ash -c "/usr/bin/qemu-arm64 /bin/busybox ls -dCFl debian/*[t]*" If that recreates it, simplify the call from there. Could you have a look at doing so Adriano or do you rely on us to try? ** Changed in: qemu (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2109627 Title: riscv64 autopkgtest failure due to missing busybox applet in test- qemu-user.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2109627/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
