Just to put the information on the bug, I reproduced this failure on a Raspberry Pi, not a piece of the Scalingstack infrastructure in sight ;-)
As far as I can tell it looked as if it's timing out waiting for network-online.target to become active. It seems as if installing network-manager makes the target take way longer to activate, so long that it is over autopkgtest's timeout. I suppose this isn't expected, so maybe the next step is to look into why that happens? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs