| 2024-01-24 13:04:52 |
Andreas Hasenack |
bug |
|
|
added bug |
| 2024-01-24 13:05:19 |
Andreas Hasenack |
libseccomp (Ubuntu): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2024-01-24 13:05:22 |
Andreas Hasenack |
libseccomp (Ubuntu): status |
New |
In Progress |
|
| 2024-01-24 13:05:36 |
Andreas Hasenack |
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. 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:
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 |
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:
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 |
|
| 2024-01-24 13:06:14 |
Andreas Hasenack |
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 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 |
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:
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 |
|
| 2024-01-24 13:06:34 |
Andreas Hasenack |
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 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 |
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 |
|
| 2024-01-24 13:23:10 |
Andreas Hasenack |
bug |
|
|
added subscriber Canonical Server |
| 2024-01-24 13:23:22 |
Andreas Hasenack |
bug |
|
|
added subscriber Ubuntu Server |
| 2024-01-24 13:23:25 |
Andreas Hasenack |
tags |
update-excuse |
server-todo update-excuse |
|
| 2024-01-29 12:31:03 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/libseccomp/+git/libseccomp/+merge/459586 |
|
| 2024-02-01 12:51:36 |
Launchpad Janitor |
libseccomp (Ubuntu): status |
In Progress |
Fix Released |
|
