From 5c44ebf96e0a90a83cb115fa6fb7013b53dcebd8 Mon Sep 17 00:00:00 2001 From: Valentin Rothberg Date: Wed, 9 Sep 2020 16:35:38 +0200 Subject: remote run: consult events for exit code After attaching to a container, we wait for the container to finish and return its exit code. Waiting for the container may not always succeed, for instance, when the container has been force removed by another process. In such case, we have to look at the *last* container-exit event. Also refactor the `ContainerRun` method a bit to return early on errors and de-spaghetti the code. Enable the remote-disabled system test. Fixes: #7117 Signed-off-by: Valentin Rothberg --- test/system/055-rm.bats | 2 -- 1 file changed, 2 deletions(-) (limited to 'test/system') diff --git a/test/system/055-rm.bats b/test/system/055-rm.bats index 478ba0f20..c8475c3e9 100644 --- a/test/system/055-rm.bats +++ b/test/system/055-rm.bats @@ -44,8 +44,6 @@ load helpers # # See https://github.com/containers/podman/issues/3795 @test "podman rm -f" { - skip_if_remote "FIXME: pending #7117" - rand=$(random_string 30) ( sleep 3; run_podman rm -f $rand ) & run_podman 137 run --name $rand $IMAGE sleep 30 -- cgit v1.2.3-54-g00ecf