I wonder what you'd think about either:
#1
--- a/debian/tests/boot-and-services
+++ b/debian/tests/boot-and-services
@@ -62,6 +62,7 @@ class ServicesTest(unittest.TestCase):
self.assertEqual(failed, [])
@unittest.skipUnless(subprocess.call(['which', 'gdm3'],
stdout=subprocess.DEVNULL) == 0, 'gdm3 not found')
+ @unittest.skipUnless(subprocess.call(['ps', 'u', '-C', 'gdm-x-session'],
stdout=subprocess.DEVNULL) == 0, 'gdm-x-session failed to start')
def test_gdm3(self):
out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])
self.assertIn(b'gdm-x-session gnome-session', out)
or
#2
--- a/debian/tests/boot-and-services
+++ b/debian/tests/boot-and-services
@@ -51,6 +51,8 @@ class ServicesTest(unittest.TestCase):
failed = [f for f in failed if 'thermald' not in f]
# console-setup.service fails on devices without keyboard (LP:
#1516591)
failed = [f for f in failed if 'console-setup' not in f]
+ # gdm lets user 118 fail (LP: #1805358)
+ failed = [f for f in failed if '[email protected]' not in f]
# cpi.service fails on s390x
failed = [f for f in failed if 'cpi.service' not in f]
if failed:
@xnox - would you have any preference between #1, #2 or neither of the above?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805358
Title:
autopkgtest boot-and-services fails on many architectures very often
since systemd/239-7ubuntu12
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805358/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
