Public bug reported: Version 2.5.4-2 introduced this change in d/t/control:
libseccomp (2.5.4-2) unstable; urgency=medium * Fix watch file. (Closes: #1050659) * Dynamically skip autopkgtests when the test runner already applies seccomp restrictions. - Drop isolation-machine restriction. -Restrictions: isolation-machine, allow-stderr +Restrictions: skippable, allow-stderr This made the test run in Ubuntu again on armhf, where we use a lxd container (it wasn't running previously). This change is relying on this check in d/t/common: if ! grep -q -E '^Seccomp:[[:blank:]]+0$' /proc/self/status; then echo "Skipping autpkgptest as the test environment already applies a seccomp filter" exit 77 fi In Debian, where they also use containers, the testsuite-live-python3 test is skipped correctly, but in Ubuntu, it is run and fails[1] with timeout limit: 541s live 541s ./regression: line 253: cd: /tmp/autopkgtest.X55y55/autopkgtest_tmp/tests/../src/python/build/lib.*: No such file or directory 10468s autopkgtest [01:49:37]: kill with SIGTERM did not work sending SIGKILL 1. https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/libs/libseccomp/20231225_015646_12139@/log.gz ** Affects: libseccomp (Ubuntu) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Tags: update-excuse ** Changed in: libseccomp (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: libseccomp (Ubuntu) Status: New => In Progress ** Description changed: Version 2.5.4-2 introduced this change in d/t/control: libseccomp (2.5.4-2) unstable; urgency=medium - * Fix watch file. (Closes: #1050659) - * Dynamically skip autopkgtests when the test runner already applies seccomp - restrictions. - - Drop isolation-machine restriction. - + * Fix watch file. (Closes: #1050659) + * Dynamically skip autopkgtests when the test runner already applies seccomp + restrictions. + - Drop isolation-machine restriction. -Restrictions: isolation-machine, allow-stderr +Restrictions: skippable, allow-stderr - - This made the test run in Ubuntu again on armhf, where we use a lxd container. This change is relying on this check in d/t/common: + This made the test run in Ubuntu again on armhf, where we use a lxd container (it wasn't running previously). This change is relying on this check in d/t/common: if ! grep -q -E '^Seccomp:[[:blank:]]+0$' /proc/self/status; then - echo "Skipping autpkgptest as the test environment already applies a seccomp filter" - exit 77 + echo "Skipping autpkgptest as the test environment already applies a seccomp filter" + exit 77 fi In Debian, where they also use containers, the test is skipped correctly, but in Ubuntu, it is run, testsuite-live-python3 fails with an infra timeout: 541s live 541s ./regression: line 253: cd: /tmp/autopkgtest.X55y55/autopkgtest_tmp/tests/../src/python/build/lib.*: No such file or directory 10468s autopkgtest [01:49:37]: kill with SIGTERM did not work sending SIGKILL ** Description changed: Version 2.5.4-2 introduced this change in d/t/control: libseccomp (2.5.4-2) unstable; urgency=medium * Fix watch file. (Closes: #1050659) * Dynamically skip autopkgtests when the test runner already applies seccomp restrictions. - Drop isolation-machine restriction. -Restrictions: isolation-machine, allow-stderr +Restrictions: skippable, allow-stderr This made the test run in Ubuntu again on armhf, where we use a lxd container (it wasn't running previously). This change is relying on this check in d/t/common: if ! grep -q -E '^Seccomp:[[:blank:]]+0$' /proc/self/status; then echo "Skipping autpkgptest as the test environment already applies a seccomp filter" exit 77 fi - In Debian, where they also use containers, the test is skipped correctly, but in Ubuntu, it is run, testsuite-live-python3 fails with an infra timeout: + In Debian, where they also use containers, the testsuite-live-python3 test is skipped correctly, but in Ubuntu, it is run and fails with timeout limit: 541s live 541s ./regression: line 253: cd: /tmp/autopkgtest.X55y55/autopkgtest_tmp/tests/../src/python/build/lib.*: No such file or directory 10468s autopkgtest [01:49:37]: kill with SIGTERM did not work sending SIGKILL ** Description changed: Version 2.5.4-2 introduced this change in d/t/control: libseccomp (2.5.4-2) unstable; urgency=medium * Fix watch file. (Closes: #1050659) * Dynamically skip autopkgtests when the test runner already applies seccomp restrictions. - Drop isolation-machine restriction. -Restrictions: isolation-machine, allow-stderr +Restrictions: skippable, allow-stderr This made the test run in Ubuntu again on armhf, where we use a lxd container (it wasn't running previously). This change is relying on this check in d/t/common: if ! grep -q -E '^Seccomp:[[:blank:]]+0$' /proc/self/status; then echo "Skipping autpkgptest as the test environment already applies a seccomp filter" exit 77 fi - In Debian, where they also use containers, the testsuite-live-python3 test is skipped correctly, but in Ubuntu, it is run and fails with timeout limit: + In Debian, where they also use containers, the testsuite-live-python3 + test is skipped correctly, but in Ubuntu, it is run and fails[1] with + timeout limit: + 541s live 541s ./regression: line 253: cd: /tmp/autopkgtest.X55y55/autopkgtest_tmp/tests/../src/python/build/lib.*: No such file or directory 10468s autopkgtest [01:49:37]: kill with SIGTERM did not work sending SIGKILL + + + 1. https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/libs/libseccomp/20231225_015646_12139@/log.gz -- 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/2051118 Title: DEP8 error on armhf Status in libseccomp package in Ubuntu: In Progress Bug description: Version 2.5.4-2 introduced this change in d/t/control: libseccomp (2.5.4-2) unstable; urgency=medium * Fix watch file. (Closes: #1050659) * Dynamically skip autopkgtests when the test runner already applies seccomp restrictions. - Drop isolation-machine restriction. -Restrictions: isolation-machine, allow-stderr +Restrictions: skippable, allow-stderr This made the test run in Ubuntu again on armhf, where we use a lxd container (it wasn't running previously). This change is relying on this check in d/t/common: if ! grep -q -E '^Seccomp:[[:blank:]]+0$' /proc/self/status; then echo "Skipping autpkgptest as the test environment already applies a seccomp filter" exit 77 fi In Debian, where they also use containers, the testsuite-live-python3 test is skipped correctly, but in Ubuntu, it is run and fails[1] with timeout limit: 541s live 541s ./regression: line 253: cd: /tmp/autopkgtest.X55y55/autopkgtest_tmp/tests/../src/python/build/lib.*: No such file or directory 10468s autopkgtest [01:49:37]: kill with SIGTERM did not work sending SIGKILL 1. https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/libs/libseccomp/20231225_015646_12139@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/2051118/+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
