** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Eoan)
Status: New => In Progress
** Changed in: systemd (Ubuntu Disco)
Status: New => In Progress
** Changed in: systemd (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu Eoan)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu Disco)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu Cosmic)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu Eoan)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Disco)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Cosmic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
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/1825997
Title:
boot-smoke test timeout too short for overloaded
autopkgtest.ubuntu.com
Status in systemd package in Ubuntu:
In Progress
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Cosmic:
In Progress
Status in systemd source package in Disco:
In Progress
Status in systemd source package in Eoan:
In Progress
Bug description:
[impact]
boot-smoke test reboots 5 times and verifies systemd is fully started
up after each boot, but only gives 35 seconds for each boot. On
loaded systems this is too short.
[test case]
see various boot-smoke failures in autopkgtest.ubuntu.com
[regression potential]
longer autopkgtest times.
[other info]
i can't reproduce this failure locally, but it seems to happen
intermittently on the adt setup. Therefore, I don't know for sure
that the short timeout is actually the cause of the problem, but it
certainly seems likely - 35 seconds really isn't very long for a full
reboot and for systemd to finish starting all services, especially on
the highly loaded autopkgtest.ubuntu.com systems.
There should be no harm, other than delaying an actual failure, from
extending the timeout. The test case checks each second if all
services have finished starting, so on success case it won't wait any
longer than it currently does.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+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
