I'd add that it seems to me the "upstream" mode of Ubuntu CI doesn't seem to be actively maintained because unlike the other CI systems used upstream (which are usually fixed almost immediately), it can be broken for weeks (or sometimes even months) which isn't suitable for CI. In principle, if nobody takes care of it, it would probably makes sense to turn off Ubuntu CI upstream (which I did) and switch to the usual release cycle where maintainers try to release the package, catch a lot of bugs (easily preventable by the CI when PRs are opened) and report them upstream. It's far from ideal, of course, but I don't know what else to do about it.
-- 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/1831296 Title: __main__.SeccompTest is failing on Ubuntu CI Status in systemd package in Ubuntu: New Status in systemd source package in Eoan: New Bug description: Since https://github.com/systemd/systemd/pull/12430 was merged and libsecomp was updated the test has been failing on Ubuntu CI: https://github.com/systemd/systemd/issues/12709. By analogy with https://github.com/systemd/systemd/pull/12430/commits/c3ab2c389ee60d92fb8d7fe779ae9c4e3c092e4c, the test should look for either "killed" or "dumped". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/+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