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)
autopkgtests pass for b/f/g
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hello Christian, or anyone else affected,
Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
@sil2100 Yes this bug has been recycled a bit too many times. We should
open a new one when the tests become flaky. The fixes related to this
bug are present in Hirsute.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
I am a bit confused on this bug. I know it's a rather 'vague' bug
describing overall flaky/troubling tests, but for instance it has been
marked as Fix Released for all the series already (groovy as well, as
this was devel back then). Now it's again present in the changelog
entries for at least the
** No longer affects: build-essential (Ubuntu)
** No longer affects: build-essential (Ubuntu Focal)
** No longer affects: glib2.0 (Ubuntu)
** No longer affects: iputils (Ubuntu)
** No longer affects: kbd (Ubuntu)
** No longer affects: linux-meta (Ubuntu)
** No longer affects: linux-meta
This bug was fixed in the package systemd - 237-3ubuntu10.43
---
systemd (237-3ubuntu10.43) bionic; urgency=medium
[ Guilherme G. Piccoli ]
* d/p/lp1830746-bump-mlock-ulimit-to-64Mb.patch:
- Bump the memlock limit to match Focal and newer releases (LP: #1830746)
This bug was fixed in the package systemd - 245.4-4ubuntu3.3
---
systemd (245.4-4ubuntu3.3) focal; urgency=medium
[ Rafael David Tinoco ]
* d/p/lp1861941-dont-generate-disk-byuuid-for-bcache-uuid.patch:
Reworded and reintroduced patch to fully explain delta is NOT a fix to
autopkgtests pass for bionic for all archs, except once for i386, for
which I opened bug 1902554; the i386 test passed on retry.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification
autopkgtests pass for focal for all archs (except i386 which is expected
to fail for focal)
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hello Christian, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Christian, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.43 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [impact]
+
+ autopkgtests are failing/flaky and prevent other packages from migrating
+ to -updates
+
+ [test case]
+
+ check systemd autopkgtest history
+
+ [regression potential]
+
+ in regard to the changed test cases, any regression would likely result
+ in
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/392373
--
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/1892358
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/392368
--
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/1892358
ok, very sorry for my delay in looking at this.
a quick scan of the results for x/b/f show:
ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r xenial -cv
--since 2month --minimum 6
parsed '2month' as '2020-08-09T14:53:00.893145-04:00'
88: boot-smoke FAIL non-zero exit
Thank you @christian. I marked the Xenial test cases under this same
bug, though can open a new bug and update the hint bug references if
needed. I'll check back to see when/if ddstreet/rbalint have a chance to
review.
For the test results you're posting, I was wondering where you're
getting
And on Bionic we only need to do so for amd64
Here is a new MP for Bionic:
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-bionic-disable-systemd-v2/+merge/390793
** Branch linked: lp:~paelzer/britney/hints-ubuntu-bionic-disable-
systemd-v2
--
You received this bug notification because
The problem with Xenial is that there it isn't just flaky "systemd-
fsckd" much more seems to be broken. I'll revise my Bionic MP, but for
Xenial I'd like to hear from ddstreet/rbalint how they think we should
go on there ...
--
You received this bug notification because you are a member of
Focal test hint was accepted tonight and things moved there.
@Kelsey - Steve denied the hint as a reset since recently a few results were
good.
Maybe you want to submit the same as force-badtest and bring it up like that
for X?
The results for xenial really look similarly bad ...
xenial
Seeing similar problems on Xenial and I suspect it's similar to the
problems occurring with Bionic and Focal:
http://autopkgtest.ubuntu.com/packages/s/systemd/xenial/amd64
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Branch linked: lp:~paelzer/britney/hints-ubuntu-focal-disable-systemd
--
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/1892358
Title:
autopkgtest success rate dropped
Thanks rbalint for pointing me to the other bug for the s390x fail we see now.
I'll continue there and consider the Groovy portion of this one closed again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
@paelzer To correct myself this (s390x) regression is not due to the
snapd seeding issue, but LP: #1895576 which may have been already fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
@paelzer I agree that the fact, i.e. that systemd autpkgtest is failing in
Groovy/s390x, but this is a real regression which is not due to flakiness of
tests-in-lxd.
Please don't reopen this bug, but file a new one or find one already opened. As
I see this is still LP: #1878225. I'm filing a
Groovy
It seems this isn't over for groovy, it was mentioned that the issues in the
subtest "tests-in-lxd" would be related to some fstab issues in those issues.
But recently all architectures, but s390x recovered. I assume that the fstab
issue is fixed but something else surfaces now.
groovy
[15:17] ddstreet: any updates on 1892358?
[15:18] @paelzer sorry not yet, i'll have systemd ready for upload
next week including fixing the autopkgtests
[15:21] ok
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
@ddstret - any update how to proceed?
If you have no time yet, then the MPs to ignore the fail until we have a new
version are up - just ack them and I guess the SRU Team will follow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
hi @cpaelzer, sorry i missed reading this earlier, i'll give all the
test failures a look to see what can be done.
--
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/1892358
If not going for marking the subtest flaky as in groovy, I have prepared
force-reset-test as alternatives in:
-
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390005
-
To match the open packages blocked on this in active releases I added
linux-meta for BIonic (thanks Kleber for the hint) and Focal (Thanks
Kelsey for the hint).
I think all of those had enough of retry-until-success and I'd ask again
for how we should proceed there. Masking/Resetting the test via
Util-linux SRU in Focal blocked as well, updating tags.
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
You received
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
True @Kleber, here the stats of Bionic - at least on x86 you seem to
have barely a chance.
bionic
amd64
boot-smoke (F 40% S 0% B 0% => P 60%/)
...F.FFF.FF.FF..
upstream (F 5% S 0% B 0% => P 95%/)
..F.
systemd-fsckd
This seems to be also affecting Bionic:
http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/amd64
We did upload new kernels, so it's difficult to isolate the issue to
systemd, but the failures are similar to what we are seeing in Focal.
--
You received this bug notification because you are
This bug was fixed in the package systemd - 246.2-1ubuntu1
---
systemd (246.2-1ubuntu1) groovy; urgency=medium
* Merge from Debian unstable
* Refresh patches
* test: accept that char device 0/0 can now be created witout privileges.
This fixes tests with Linux 5.8 and later
Here an (monospace) overview of recent focal tests.
focal
amd64
networkd-testpy(F 5% S 0% B 5% => P 90%/)
.B...F..
boot-and-services (F 5% S 0% B 5% => P 90%/)
.B...F..
upstream (F 5% S 0% B 5% =>
https://launchpad.net/ubuntu/+source/systemd/246.2-1ubuntu1 is still in
proposed and I was looking forward to a bunch of custom triggers this
morning.
But I found everything migrated this morning despite those new tests not being
done.
What is left is the similar situation in Focal (as mentioned before).
I have updated the tasks to reflect that properly and get update-excuse tagging
there.
In Focal it is currently blocking qemu and build-essential SRUs and I
wanted to ask if the plan is to do the same upload+test-reset there
[16:34] seb128, cpaelzer ahasenack sorry, i was out and apparently
forgot setting that in my email. the last systemd upload should fix everything
except for the livecd-rootfs revert that made fstab in lxd images invalide
[16:45] rbalint: " the last systemd upload" means groovy I guess,
what
@paelzer The fstab bug is LP: #1877078, I'm waiting for @vorlon's
comment's about what his plan is after his revert.
--
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/1892358
Adding glib2.0 as it had a rebuild for libffi and will be blocke dby
this as well.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glib2.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Added another two packages that are blocked by this so they are
marked/linked in update excuses :-/
** Also affects: iputils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: iputils (Ubuntu)
Status: New => Confirmed
** Also affects: ntpsec (Ubuntu)
Importance:
Adding update-excuse tag so that one can find this issue from update-excuses
page.
To show up at the packages that fail I also add an qemu and kbd task (more
might pile up)
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Also affects: kbd (Ubuntu)
Importance: Undecided
Thank you Rbalint.
Thanks to xnox I already found 1891716 and 1886886 which are sort of
remotely related (to the next upload), I guess this bug will serve for
the "marking systemd-fsckd test as flaky" task then.
Can we do something about this bad fstab in LXD or is there a bug to
track?
Tests-in-lxd fails because LXD images ship invalid /etc/fstab again making
systemd-remount-fs.service fail.
I'm marking systemd-fsckd test as flaky to not block others' work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags added: rls-gg-incoming
--
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/1892358
Title:
autopkgtest success rate dropped inhibiting proposed migration
Status in
47 matches
Mail list logo
