Comment 0 for bug 1825997
Revision history for this message
| Dan Streetman (ddstreet) wrote boot-smoke test timeout too short for overloaded autopkgtest.ubuntu.com | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
[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.
[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.
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.