I'm assigning launchpad, maybe somebody can try notmuch/armhf with an
updated qemu or a downgraded kernel :)
--
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 (
Yes, the nature of the bug makes impossible to do as requested by the
bot…
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707409
T
** Tags removed: precise
** Tags added: bot-stop-nagging xenial
--
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
To manage noti
I think it's very unlikely indeed that this is a Launchpad bug, and
we're not here to go on fishing expeditions for you testing random
things. qemu/kernel developers are generally better placed to be able
to bisect this sort of thing. Of course you can reopen this if there
turns out to be some ev
TL;DR:
- you can use the pbuilder + static qemu setup to debug
- qemu/libvirt throw no error
- the tests do not "consider" the unsupported syscall
- I found to get just the same issues on Artful but with more context
indicating that missing syscall
- You can use the setup described above (or sbuil
>And with that finally I found:
>override_dh_auto_test:
>ifeq ($(DEB_HOST_ARCH),armhf)
>TERM=vt100 dh_auto_test || true
>Which means it is not meant/expected to work properly on archhf.
sure, I put that *because* of this bug :) it is quite the opposite,
since qemu or something else throws
+qemu: Unsupported syscall: 384
+qemu: Unsupported syscall: 26
+exit status: 255
I would say that missing syscall 384 and 26 are the culprit?
** Changed in: qemu (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
well, some tests are failing just because of 384 non implemented on artful
T150-tagging: Testing "notmuch tag"
FAIL Xapian exception: read only files
--- T150-tagging.24.expected2017-08-08 10:28:25.0 +
+++ T150-tagging.24.output 2017-08-08 10:28:25.0
Setting qemu task to invalid per Colins explanation that the LP case
doesn't use it.
** Changed in: qemu (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707
qemu isn't involved. We intentionally run armhf builds on an arm64
kernel (with an appropriate personality set) because this allows us to
make denser use of our build resources; I don't expect this to change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Interesting, so somewhat the system is triggering an illegal arm64
instruction? Can be that gdb needs somebody telling it to use armhf
platform?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707409
T
I agree on 384 being getrandom and there are other cases like [1].
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?
>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
>
There is two issues being mixed up here
1) launchpad buildd changes.
notmuch build system appears to be confused by the new enviroment. It
appears ubuntu has chosen "armhf chroot on arm64 machine" approach,
which would mean qemu system call emulation is not involved. if it is -
it a buildd config
** Changed in: launchpad-buildd
Status: Invalid => New
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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:
testsui
Well, LP builders have qemu 2.5, so this might be true for the syscall.
However, I appreciate the first point, this is in-line with my
expectations and might be solvable by launchpad buildd team admins.
Can you please have a deeper look now?
thanks!
--
You received this bug notification becaus
16 matches
Mail list logo
