Comment 0 for bug 2051118

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