>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 illegal instruction, I had to
disable the testsuite.

G.

please use the debian package when doing things, the Ubuntu one has the
gdb missing and other hacks (and please use the latest version)

(I'm trying with the same setup as you, but I don't think I have the
knowledge to trace down this bug further)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1707409

Title:
  testsuite fails under qemu (SIGILL) works fine on real hw

Status in launchpad-buildd:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Hello, after spending a lot of time debugging notmuch failure under
  armhf, we came to a conclusion:

  it started to fail when the infra moved to a new kernel 3.2 to a 4.2,
  and moved under qemu/kvm environment.

  the latest successful build is here  created on 2016-03-13
  https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826

  and the first bad is this one:  Started on 2016-08-31
  https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/10600002

  Kernel version: Linux kishi10 3.2.0-98-highbank #138-Ubuntu SMP PREEMPT Mon 
Jan 11 13:24:41 UTC 2016 armv7l
  Kernel version: Linux bos01-arm64-024 4.2.0-42-generic #49-Ubuntu SMP Tue Jun 
28 21:24:20 UTC 2016 aarch64

  so, in the first case armhf was ran on top of an armv7 kernel, in the other 
case it became an arm64 one
  this might not even be a regression in qemu/kvm, but rather a change in 
buildd system that spot a new bug

  doing a xenial build failed aswell, so I presume this is not a
  toolchain regression (also because it works fine on real HW), but a
  qemu/linux bug.

  I did run the test under strace/valgrind, I can't do much more testing, but I 
hope the logs can be useful for you
  
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431
  
https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz

  You can see the strace/valgrind outputs between "BEGIN" and "END"
  keywords

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to