Build issue is reproducible on arm64 LP infrastructure builds.

I spawned a canonistack arm64 system to check if it is reproducible
there as well for some debugging how we could fix it.

Interestingly, it does NOT FAIL on focal as-is when building on aarch64.

But as LP builds are against -proposed I Then switched to focal-proposed which 
upgraded this list of things:
apport/focal-proposed 2.20.11-0ubuntu11 all [upgradable from: 2.20.11-0ubuntu9]
fwupd-signed/focal-proposed 1.12+1.3.3-2 arm64 [upgradable from: 
1.10+1.2.10-1ubuntu2]
fwupd/focal-proposed 1.3.3-2 arm64 [upgradable from: 1.2.10-1ubuntu2]
gawk/focal-proposed 1:5.0.1+dfsg-1 arm64 [upgradable from: 
1:4.2.1+dfsg-1.1build1]
libcap2-bin/focal-proposed 1:2.27-1 arm64 [upgradable from: 1:2.25-2]
libcap2/focal-proposed 1:2.27-1 arm64 [upgradable from: 1:2.25-2]
libdebconfclient0/focal-proposed 0.250ubuntu1 arm64 [upgradable from: 
0.249ubuntu1]
libfwupd2/focal-proposed 1.3.3-2 arm64 [upgradable from: 1.2.10-1ubuntu2]
libglib2.0-0/focal-proposed 2.63.1-1 arm64 [upgradable from: 2.62.1-1]
libglib2.0-bin/focal-proposed 2.63.1-1 arm64 [upgradable from: 2.62.1-1]
libglib2.0-data/focal-proposed 2.63.1-1 all [upgradable from: 2.62.1-1]
liblz4-1/focal-proposed 1.9.2-1 arm64 [upgradable from: 1.9.1-2]
libpam-cap/focal-proposed 1:2.27-1 arm64 [upgradable from: 1:2.25-2]
libpython3-all-dev/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 
3.7.5-1]
libpython3-dev/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1]
libpython3-stdlib/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1]
libseccomp2/focal-proposed 2.4.1-0ubuntu0.19.10.4 arm64 [upgradable from: 
2.4.1-0ubuntu0.19.10.3]
linux-headers-generic/focal-proposed 5.3.0.21.24 arm64 [upgradable from: 
5.3.0.19.22]
linux-headers-virtual/focal-proposed 5.3.0.21.24 arm64 [upgradable from: 
5.3.0.19.22]
linux-image-virtual/focal-proposed 5.3.0.21.24 arm64 [upgradable from: 
5.3.0.19.22]
linux-libc-dev/focal-proposed 5.3.0-21.22 arm64 [upgradable from: 5.3.0-19.20]
linux-virtual/focal-proposed 5.3.0.21.24 arm64 [upgradable from: 5.3.0.19.22]
lz4/focal-proposed 1.9.2-1 arm64 [upgradable from: 1.9.1-2]
python3-all-dev/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1]
python3-all/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1]
python3-apport/focal-proposed 2.20.11-0ubuntu11 all [upgradable from: 
2.20.11-0ubuntu9]
python3-colorama/focal-proposed 0.4.1-1 all [upgradable from: 0.3.7-1]
python3-dev/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1]
python3-distupgrade/focal-proposed 1:20.04.4 all [upgradable from: 1:20.04.2]
python3-jwt/focal-proposed 1.7.1-2 all [upgradable from: 1.7.1-1]
python3-launchpadlib/focal-proposed 1.10.7-2 all [upgradable from: 1.10.7-1]
python3-lazr.restfulclient/focal-proposed 0.14.2-2 all [upgradable from: 
0.14.2-1]
python3-lazr.uri/focal-proposed 1.0.3-4 all [upgradable from: 1.0.3-3]
python3-minimal/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1]
python3-oauthlib/focal-proposed 3.1.0-1 all [upgradable from: 2.1.0-1]
python3-pkg-resources/focal-proposed 41.4.0-1 all [upgradable from: 41.1.0-1]
python3-problem-report/focal-proposed 2.20.11-0ubuntu11 all [upgradable from: 
2.20.11-0ubuntu9]
python3-twisted-bin/focal-proposed 18.9.0-4 arm64 [upgradable from: 
18.9.0-3ubuntu1]
python3-twisted/focal-proposed 18.9.0-4 all [upgradable from: 18.9.0-3ubuntu1]
python3-wadllib/focal-proposed 1.3.3-3 all [upgradable from: 1.3.3-2]
python3/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1]
ubuntu-release-upgrader-core/focal-proposed 1:20.04.4 all [upgradable from: 
1:20.04.2]


I especially wanted to check linux-libc-dev as that brings the headers used 
here:

That 5.3.0-19.20 is actually newer and just in the image.
There is a 5.3.0-18.19 from http://us.ports.ubuntu.com/ubuntu-ports focal/main.
So maybe instead of upgrading the trigger is downgrading to that?


Fail: LP build (two days ago): 5.3.0-18.19
Fail: LP build (rebuild today): 5.3.0-18.19
Good: canonistack (focal image): 5.3.0-19.20
Good: canonistack (focal-proposed): 5.3.0-21.22
Good: canonistack (focal-release): 5.3.0-18.19

This isn't very insightful, it just always works except in LP builders :-/
The difference in the package version, even when rebuilding is odd, but at 
least in the tests wasn't the reason.

For now I'm scratching my head and will hit rebuild tomorrow again ...
?!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1849785

Title:
  FTBFS on i386/ppc64/s390x (Eoan+Focal)

Status in libseccomp:
  Fix Released
Status in libseccomp package in Ubuntu:
  Triaged
Status in libseccomp source package in Eoan:
  Triaged

Bug description:
  Due to the python 3.8 transition in focal this was rebuilt but fails atm.
  => 
https://launchpadlibrarian.net/448119198/buildlog_ubuntu-focal-s390x.libseccomp_2.4.1-0ubuntu0.19.10.4_BUILDING.txt.gz

  The simulations fail in this case:
   batch name: 36-sim-ipc_syscalls
   test mode:  c
   test type:  bpf-sim
  Test 36-sim-ipc_syscalls%%001-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%002-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%003-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%004-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%005-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%006-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%007-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%008-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%009-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%010-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%011-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%012-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%013-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%014-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%015-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%016-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%017-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%018-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%019-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%020-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%021-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%022-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%023-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%024-00001 result:   ERROR 36-sim-ipc_syscalls rc=14
   test mode:  c
   test type:  bpf-valgrind
  Test 36-sim-ipc_syscalls%%025-00001 result:   FAILURE 36-sim-ipc_syscalls 
rc=14
   batch name: 37-sim-ipc_syscalls_be
   test mode:  c
   test type:  bpf-sim
   test arch:  s390

  
   batch name: 37-sim-ipc_syscalls_be
   test mode:  c
   test type:  bpf-sim
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%001-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%002-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%003-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%004-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%005-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%006-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%007-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%008-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%009-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%010-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%011-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%012-00001 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test mode:  c
   test type:  bpf-valgrind
  Test 37-sim-ipc_syscalls_be%%013-00001 result:   FAILURE 
37-sim-ipc_syscalls_be rc=14

  
  It is always the s390x test - even when running on i386/ppc64
  On x86_64 this test succeeds:

  Test 36-sim-ipc_syscalls%%025-00001 result:   SUCCESS
   batch name: 37-sim-ipc_syscalls_be
   test mode:  c
   test type:  bpf-sim
   test arch:  s390

To manage notifications about this bug go to:
https://bugs.launchpad.net/libseccomp/+bug/1849785/+subscriptions

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

Reply via email to