Use their $AUTOPKGTEST_* equivalents.
These were introduced in autopkgtest 4.0 (June 2016), and all our CI
systems use a much newer version.
Gbp-Dch: Short
In some cases ActiveEnterTimestampMonotonic is zero even for units that did
run. Stop trying to interpret individual properties and just rely on "systemctl
status" to do it for us.
This also shows the complete status output on test failure, which eases
debugging.
LP: #1624406
The start time apparently does not appear in the ExecStart= property any more.
Query ActiveEnterTimestampMonotonic instead, which is a more "official"
property.
Also change is_active_unit() to allow easier debugging.
... instead of 90-autopkgtest.cfg. The latter does not exist on non-x86
architectures and is not relevant for this test.
This should fix the non-rebooting ppc64el instances in Ubuntu CI.
I. e. the initramfs already ran fsck. Then systemd-fsck-root, fsckd etc. are
not supposed to run.
This is currently hidden by http://bugs.debian.org/783291, but once that gets
fixed this will cause the systemd-fsckd test to fail with current
initramfs-tools.
They are mostly testing the robustness of the various daemons:
- starting with or without plymouth
- surviving kill of fsck, systemd-fsckd, systemd-fsck, plymouth
It will be possible to extend it later on with Control+C tests on plymouth
and eventually checking the protocol output.
LP: #1427312
