The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1933090 Title: systemd/245.4-4ubuntu3.6 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Won't Fix Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in linux-hwe-5.11 source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Bug description: [SRU Impact] Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c, test_protect_syscall sysctl is called with the expectation the error result is EFAULT and not ENOSYS. This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp, oem, gke, oracle). [Fix] Assertion checks if either EFAULT or ENOSYS is returned. This way it will work for focal-5.4 kernels and focal-5.15 kernels. [Test to reproduce the issue] 1. Create a vm and install one of the focal-5.15 kernels (i.e 5.15.0-1029.35~20.04.1 linux-oracle-5.15). 2. Run the autotests for upstream and/or root-unittests: autopkgtest --test-name=upstream systemd -- qemu <vm_image> [Test to verify the fix] 1. Same as above 2. Apply the fix in your local repo and run the tests using your local repo autopkgtest --test-name=upstream <path to systemd> -- qemu <vm_image> [Where problems could occur] This is not gonna affect end users since it is a change in the test only. It may impact autotests, but it's a very low probability. [Original Description] This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz In arm64, ppc64el and s390x, 'root-unittests' fails with: /* test_protect_sysctl */ Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function test_protect_sysctl(). A borting. sysctlseccomp terminated by signal ABRT. Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == EXIT_SUCCESS' failed at s rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting. FAIL: test-seccomp (code: 134) In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which apparently is caused by the same 'test-seccomp.c:311' assertion failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+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
