This bug was fixed in the package systemd - 246.6-1ubuntu1
---
systemd (246.6-1ubuntu1) groovy; urgency=medium
[ Dan Streetman ]
* Fix resolved.conf Cache= default to match default (LP: #1895418)
Files:
- debian/patches/lp1895418.patch
I can't start s390x VMs to reproduce it for some reason so I'm just
disabling this test in the next upload.
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, the next upload passes on s390x, so this will likely be resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895576
Title:
boot-and-services in tests-in-lxd autopkgtest fails in groovy on
For now the hint is in groovy, but the next systemd upload needs to
resolve it one (fix) or the other (mark this one as flaky) way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895576
Title:
The retries were reproducible failing as well.
[09:20] rbalint: btw the test on s390x really seems still broken
[09:20] we need either a fix or a test hint
[09:21] --> falcojr (~falcojr@184.55.64.152) has joined this channel.
[09:24] cpaelzer, i'm ok with the hint and i've retriggered the
Old hints we only had:
# failing due to multiple reasons LP: #1892358
force-badtest systemd/246-2ubuntu1
# failing due to livecd-rootfs creating broken LXD images LP: #1877078
force-reset-test systemd/246.2-1ubuntu1
But was then removed in
revno: 4988
committer: Steve Langasek
branch nick:
Also please do note that while almost all of the recent tests failed - almost
all of the packages already migrated. Why is that - there is no test hint in
place.
For example gdm3/3.37.90-1ubuntu1 and iptables/1.8.4-3ubuntu3 (but more than
just those, policykit-1, dpdk, util-linux, ...) NEVER
@Rbalint - hi the two most recent tests confirm that it still seems broken.
Maybe the good run was a one-off lucky run ... :-/
I'd ask you to look into that a bit deeper as it will again hold back
plenty of things in groovy soon.
--
You received this bug notification because you are a member of
Thanks for this bug Rbalint.
That the new glibc/cryptsetup worked is odd as nothing on the issue indicates
they are related. There was nothing in the queue - for the sake of some test
data I have restarted the packages currently blocked on this with all-proposed
which will pull in e.g.
