[Bug 1975587] Autopkgtest regression report (systemd/245.4-4ubuntu3.19)
Ubuntu SRU Bot
1975587 at bugs.launchpad.net
Fri Oct 21 20:56:56 UTC 2022
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.19) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
linux-aws-5.13/5.13.0-1031.35~20.04.1 (amd64)
munin/2.0.56-1ubuntu1 (arm64)
linux-gcp-5.8/5.8.0-1039.41 (amd64)
gvfs/1.44.1-1ubuntu1.1 (amd64)
linux-gcp-5.11/5.11.0-1030.34~20.04.3 (amd64)
linux-hwe-5.15/5.15.0-52.58~20.04.1 (amd64)
linux-oem-5.13/5.13.0-1029.36 (amd64)
systemd/245.4-4ubuntu3.19 (armhf)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1975587
Title:
systemd: fix test-execute autotest failure with kernel 5.15 in focal
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Bug description:
[Impact]
test-execute autotest is failing in focal with kernel 5.15. This is
because the following kernel commit changed the ABI for ioprio:
e70344c05995 ("block: fix default IO priority handling")
Previously setting IOPRIO_CLASS_NONE for a process would report
IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
IOPRIO_CLASS_BE instead.
[Test case]
Run systemd autopkgtest and check for the test-execute result.
[Fix]
Change test/test-execute/exec-ioschedulingclass-none.service to
recognize both "none" and "best-effort" as valid returned strings from
ionice.
This change is already available in jammy and above.
[Regression potential]
We may see regressions in systemd autopkgtest, we won't introduce any
potential regressions in systemd itself, because this is only
affecting the specific unit test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+subscriptions
More information about the foundations-bugs
mailing list