Frantisek Sumsal
ed0727fecd
test: sync the journal before checking it for ordering cycle messages
Otherwise we might get an empty match:
TEST-03-JOBS.sh[100]: + IDS_FILE=/tmp/TEST-03-JOBS-CYCLE-IDS-30241
TEST-03-JOBS.sh[314]: + varlinkctl call /run/systemd/io.systemd.Manager io.systemd.Manager.Describe '{}'
TEST-03-JOBS.sh[315]: + jq .runtime.TransactionsWithOrderingCycle
TEST-03-JOBS.sh[316]: ++ jq length /tmp/TEST-03-JOBS-CYCLE-IDS-30241
TEST-03-JOBS.sh[100]: + [[ 20 -ge 20 ]]
TEST-03-JOBS.sh[100]: + for i in {0..19}
TEST-03-JOBS.sh[317]: ++ jq -r '.[0]' /tmp/TEST-03-JOBS-CYCLE-IDS-30241
TEST-03-JOBS.sh[100]: + journalctl -b TRANSACTION_ID=48 --grep 'cycle starting with'
TEST-03-JOBS.sh[318]: -- No entries --
[FAILED] Failed to start TEST-03-JOBS.service - TEST-03-JOBS.
[ !! ] Exiting: unit TEST-03-JOBS.service failed
Even though the message was properly emitted:
$ journalctl --file TEST-03-JOBS-1.journal -b TRANSACTION_ID=48 --grep 'cycle starting with'
Aug 11 14:46:15 H systemd[1]: [🡕] transaction-cycle17.service: Unable to break cycle starting with transaction-cycle17.service/start
2026-08-11 16:12:42 +02:00
..
2026-07-16 01:23:40 +09:00
2026-08-07 11:56:44 +02:00
2026-08-04 08:08:33 +09:00
2025-09-04 14:36:46 +09:00
2025-09-04 14:36:46 +09:00
2026-07-31 10:46:50 +09:00
2026-06-03 20:21:54 +01:00
2026-04-20 09:37:13 +02:00
2026-07-20 14:35:04 +09:00
2025-12-20 18:31:55 +01:00
2026-08-04 08:17:04 +09:00
2026-08-11 16:12:42 +02:00
2026-05-18 02:44:46 +09:00
2023-12-19 16:01:54 +01:00
2026-08-05 11:37:29 +09:00
2026-05-18 02:44:46 +09:00
2026-05-18 02:44:46 +09:00
2026-05-18 02:44:46 +09:00
2026-05-18 02:44:46 +09:00
2026-08-03 13:54:17 +09:00
2025-11-17 16:50:50 +01:00
2026-07-12 23:31:29 +02:00
2024-09-18 09:47:04 +09:00
2026-05-24 14:12:50 +01:00
2024-05-15 18:25:27 +02:00
2026-06-20 01:41:46 +01:00
2026-07-26 15:10:33 +09:00
2026-06-21 18:20:53 +01:00
2026-08-04 08:17:04 +09:00
2026-08-03 13:54:17 +09:00
2026-01-21 12:03:07 +01:00
2020-03-28 11:46:48 +01:00