Yu Watanabe

test: sync journal before starting test

1

Follow-up for c22a112883a46e302dae587b809c459647363ceb. Hopefully fixes #32712.

https://github.com/systemd/systemd/actions/runs/9145488734/job/25144487816?pr=32921 ``` [ 120.476479] TEST-35-LOGIN.sh[2333]: ++ journalctl -b -u systemd-logind.service --since=06:56:32 --grep 'Session "17" of user "logind-test-user" is idle, stopping.' [ 120.486364] TEST-35-LOGIN.sh[2334]: ++ wc -l [ 120.495612] TEST-35-LOGIN.sh[2184]: +...

machine-id-setup: acquire machine ID from /run/machine-id if possible

1

If machine ID is previously stored at /run/machine-id, then let's reuse it. This is important on switching root and /etc/machine-id was previously a mount point. Fixes https://github.com/systemd/systemd/issues/32908.

TEST-85-NETWORK-NetworkdSRIOVTests failed in GitHub Actions

3

https://github.com/systemd/systemd/actions/runs/9137583438/job/25127740138?pr=32907 ``` gh run download 9137583438 --name ci-mkosi-9137583438-1-arch-rolling-failed-test-journals -D ci/ci-mkosi-9137583438-1-arch-rolling-failed-test-journals ```

units: also swap ordering of systemd-exit.service vs exit.target and friends

8

Follow-up for 4263d7617f0e6ea741e227db223ac6085479165f (#32880). Otherwise, the targets cannot be used as a synchronization point.

mkosi: machine ID in initrd and host are different??

1

There are two journal directories. ``` May 18 04:03:30 journalctl[1421]: Considering root directory '/run/log/journal'. May 18 04:03:30 journalctl[1421]: Root directory /run/log/journal added. May 18 04:03:30 journalctl[1421]: Considering directory '/run/log/journal/349ddf49b1a6401384f5251832e4f9b1'. May...

analyze: make systemd-analyze verify/security work for transient units

2

Closes #32824.

'udevadm wait' should optionally wait for .device unit being activated

2

https://github.com/systemd/systemd/pull/32887#issuecomment-2116888681

core/mount: unmount credential directory with relevant mount unit

4

Replaces 1e1225614ca1106116dcad9fb37aaeb6106408ab. When exec_context_destroy_credentials() -> umount2() succeeds, the relevant .mount unit may be already already in deactivating but umount command may not be invoked yet. In such case, the later...