From 371c4bd341d34f2b1a9a2e95974b5bfe8ff56343 Mon Sep 17 00:00:00 2001 From: Chris Evich Date: Fri, 17 Apr 2026 10:28:59 -0400 Subject: [PATCH] Fix system test: podman logs restarted journald When run with `podman-remote`, the `--events-backend` option is unavailable. However, the `podman logs restarted journald` test blindly sets `events_backend` without checking if the remote client is being used. This causes the test to fail. Fix this by skipping the test when the remote client is being used. Signed-off-by: Chris Evich --- test/system/035-logs.bats | 3 +++ 1 file changed, 3 insertions(+) diff --git a/test/system/035-logs.bats b/test/system/035-logs.bats index 6b8d5fbc5f..0d88428ada 100644 --- a/test/system/035-logs.bats +++ b/test/system/035-logs.bats @@ -120,6 +120,9 @@ ${cid[0]} d" "Sequential output from logs" function _log_test_restarted() { local driver=$1 local events_backend=$(_additional_events_backend $driver) + if [[ -n "${events_backend}" ]]; then + skip_if_remote "remote does not support --events-backend" + fi run_podman run --log-driver=$driver ${events_backend} --name logtest $IMAGE sh -c 'start=0; if test -s log; then start=`tail -n 1 log`; fi; seq `expr $start + 1` `expr $start + 10` | tee -a log' # FIXME: #9597 # run/start is flaking for remote so let's wait for the container condition