This bug was fixed in the package systemd - 246.6-1ubuntu1.1
---------------
systemd (246.6-1ubuntu1.1) groovy; urgency=medium
[ Dan Streetman ]
* d/t/boot-smoke: update test to avoid false negatives
(LP: #1892358)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=205c30ca53b0e421db28bb56afaf5f88650ce592
* d/t/boot-and-services: remove unneeded test lines
(LP: #1892358)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=71853082af4e668996db574915c5a156f9897fd3
* d/t/systemd-fsckd: rewrite test to try to fix false negatives
(LP: #1892358)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6ae6be039ec582410769d2d6d131e12bdcd19a68
* d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch:
test: use cap_last_cap() instead of capability_list_length()
(LP: #1905044)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=84a4832f5f7d4f939c1c78c6be4c3f9e05cd7f59
*
d/p/lp1907306/0001-sd-dhcp-client-don-t-log-timeouts-if-already-expired.patch,
d/p/lp1907306/0002-sd-dhcp-client-track-dhcp4-t1-t2-expire-times.patch,
d/p/lp1907306/0003-sd-dhcp-client-add-RFC2131-retransmission-details.patch,
d/p/lp1907306/0004-sd-dhcp-client-simplify-dhcp4-t1-t2-parsing.patch,
d/p/lp1907306/0005-sd-dhcp-client-correct-dhcpv4-renew-rebind-retransmi.patch,
d/p/lp1907306/0006-sd-dhcp-client-correct-retransmission-timeout-to-mat.patch,
d/p/lp1907306/0007-test-network-increase-wait_online-timeout-to-handle-.patch,
d/p/lp1907306/0008-sd-dhcp-client-fix-renew-rebind-timeout-calculation-.patch:
Send correct number of dhcpv4 renew and rebind requests
(LP: #1907306)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0a96dc16ac00e90cd3904e6d490d676b9bb98f1f
* d/p/lp1902960-udev-re-assign-ID_NET_DRIVER-ID_NET_LINK_FILE-ID_NET.patch:
Run net_setup_link on 'change' uevents (LP: #1902960)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7183e2ef4758ce47b152dec735e7d213d6003e37
* d/t/root-unittests:
Remove any corrupt journal files (LP: #1881947)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3d0ea66f0db4a204759fa0005f6f27579ee4195a
[ Balint Reczey ]
* d/t/systemd-fsckd: Plymouth-start stays active in 20.10 and later
(LP: #1908067)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e3ddd09301c8bdaa59b4fe54d7906f609552370d
-- Dan Streetman <ddstr...@canonical.com> Wed, 06 Jan 2021 15:40:39
-0500
** Changed in: systemd (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
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/1905044
Title:
systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Groovy:
Fix Released
Status in systemd source package in Hirsute:
Fix Released
Bug description:
[impact]
autopkgtest failure when running with 5.8 kernel, if systemd is built
with earlier kernel (e.g. 5.4)
[test case]
see autopkgtest results, e.g. links in original description below
[regression potential]
as this only fixes a test case, any regression would likely result in
an incorrectly passing, or incorrectly failing, test.
[scope]
this is needed for b/f/g/h.
this bug was introduced by upstream commit 23cc81e7c22 which first
added testing for 'invalid' cap numbers, but incorrectly using
capability_list_length() instead of cap_last_cap(). That commit was
first included in v236, so this bug does not exist before Bionic.
this is fixed upstream by commit
ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in
v247, so this is needed for h and earlier.
Also note that even though the 5.8 kernel is not planned to be
released for Bionic, this test also runs at build time, and since the
LP build farm builds inside chroots, if the build farm ever moved up
to Focal with a 5.8 kernel, the build of systemd for Bionic would
start failing (since it would still be building using the older kernel
headers, inside the chroot), so this does need to be fixed in Bionic
systemd as well.
[other info]
there is a non-test bug related to this in bug 1905245
[original description]
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz
The failing testcases are:
- root-unittests
Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at
src/test/test-cap-list.c:60, funct
ion test_capability_set_one(). Aborting.
FAIL: test-cap-list (code: 134)
- upstream
TEST-24-UNIT-TESTS:
--- test-cap-list begin ---
Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at
src/test/test-cap-list.c:60, funct
ion test_capability_set_one(). Aborting.
--- test-cap-list end ---
Both seem to be failing with the same assertion.
These tests are successful on Focal with linux 5.4, therefore they
would regress when upgrading the kernel from 5.4 to 5.8.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+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
