From 34137c40f65489727fc330e9fc378f13e1baae0a Mon Sep 17 00:00:00 2001 From: Paul Holzinger Date: Wed, 27 May 2026 12:03:02 +0200 Subject: [PATCH] test/system: fix "podman stop - unlock while waiting for timeout" In highly parallel runs this can fail its timeout due the fact that we run podman ps -a which takes all contianer locks, even the ones from unrelated tests. thus this command can take a long time, from a CI log I see: [18:22:30.932958589] # /var/tmp/podman/bin/podman ps -a [18:22:34.338904713] CONTAINER ID IMAGE So like a 4s delay just on that and hence the test later failed with "Operations took too long" as it took 7 seconds overall. So since we know podman inspect takes the lock just keep that and not try to get all containers for no reason. Signed-off-by: Paul Holzinger --- test/system/050-stop.bats | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/test/system/050-stop.bats b/test/system/050-stop.bats index 59c4576e1f..032c6b293d 100644 --- a/test/system/050-stop.bats +++ b/test/system/050-stop.bats @@ -198,9 +198,7 @@ load helpers sleep 0.5 done - # Other commands can acquire the lock - run_podman ps -a - + # This command must be able to take the container lock. # The container state transitioned to "stopping" run_podman inspect --format '{{.State.Status}}' $ctrname is "$output" "stopping" "Status of container should be 'stopping'"