Skip to content

Commit c4c2778

Browse files
committed
test/system: fix "podman kill - concurrent stop"
It is possible that the background podman stop -t 1 completes before we get to podman kill making the kill fail as the container is not running. The result is this error in the test: "Error: can only kill running containers. xxx is in state exited: container state improper" We can just bump the stop timeout to have a larger time where we can trigger kill on a stopping container. Signed-off-by: Paul Holzinger <pholzing@redhat.com>
1 parent ea51ae7 commit c4c2778

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

test/system/130-kill.bats

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ load helpers
124124
# 14761 - concurrent kill/stop must record the exit code
125125
cname=c-$(safename)
126126
run_podman run -d --replace --name=$cname $IMAGE sh -c "trap 'echo Received SIGTERM, ignoring' SIGTERM; echo READY; while :; do sleep 0.2; done"
127-
"${PODMAN_CMD[@]}" stop -t 1 $cname &
127+
"${PODMAN_CMD[@]}" stop -t 5 $cname &
128128
run_podman kill $cname
129129
run_podman wait $cname
130130
run_podman rm -f $cname

0 commit comments

Comments
 (0)