Test suite reports incomplete (and thus useless) info when systemctl is-system-running fails
Listing the units is not enough: in most cases I've seen,
is-system-running returns "starting" which means the job queue is not empty, and to debug that we need the list of jobs.
I'm aware anonym and I might not agree about whether we should run
is-system-running in "Tor is ready", but I think we have another ticket to discuss that, and regardless where this code moves the proposed change will be useful so let's not block on orthogonal discussions :)
Test suite: log the list of systemd jobs when systemctl is-system-running fails (refs: #14772).
Listing the units is not enough: in most cases I've seen, is-system-running
returns "starting" which means the job queue is not empty, and to debug that we
need the list of jobs.
Merge remote-tracking branch 'origin/test/14772-log-more-useful-info-when-is-system-running-fails' into devel
Test suite: allow more time for 'systemctl is-system-running' to succeed.
Hypothesis: #14772 is due to a race occurring after `step "the time
has synced"`, namely that the systemd units that will start when the
time is synced (and probably the same check is used for this as in
that step) haven't necessarily finished when we run `systemctl
is-system-running`. So let's just give it some more time.
- Status changed from In Progress to Fix committed
- Assignee deleted (
- % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
Merged! As discussed on XMPP, I also committed dd985681bfc29f0fdf00a4ac762208b215579be7 on top (and now I realize its
Will-fix: probably should've been a
Refs:), which actually might also solve the root cause for this error. We'll see!