>I agree on 384 being getrandom and there are other cases like [1]. I did the same research :)
>I don't know details but would consider the pure lack of the system call >support a feature request to >upstream qemu. >We could add a qemu upstream task here for that FR - in the worst case we are >told why we are wrong - >opinions? yes please! >On the case itself for now I'd recommend to get back the section: >ifeq ($(DEB_HOST_ARCH),armhf) > TERM=vt100 dh_auto_test || true > >Which maybe was there for similar reasons. I think this used to hang the builders, IIRC, but seems to pass now https://launchpadlibrarian.net/332584378/buildlog_ubuntu-artful-armhf.notmuch_0.25-4ubuntu1_BUILDING.txt.gz uploaded in artful G. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707409 Title: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall] To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
