Files
podman/test/e2e
Ed Santiago 1c59a9ced1 CI: safer podman-stop tests
A number of tests start a container then immediately run podman stop.
This frequently flakes with:

   StopSignal SIGTERM failed to stop [...] in 10 seconds, resorting to SIGKILL

Likely reason: container is still initializing, and its process
has not yet set up its signal handlers.

Solution: if possible (containers running "top"), wait for "Mem:"
to indicate that top is running. If not possible (pods / catatonit),
sleep half a second.

Intended to fix some of the flakes cataloged in #20196 but I'm
leaving that open in case we see more. These are hard to identify
just by looking in the code.

Signed-off-by: Ed Santiago <santiago@redhat.com>
2023-12-14 04:49:46 -07:00
..
2023-12-14 04:49:46 -07:00
2023-11-17 05:48:50 -07:00
2023-11-17 05:48:50 -07:00
2023-11-17 05:48:50 -07:00
2023-10-23 11:50:41 -06:00
2023-09-12 13:47:35 -06:00
2023-09-25 11:48:35 +02:00
2023-10-23 11:50:41 -06:00
2023-11-17 05:48:50 -07:00
2023-12-14 04:49:46 -07:00
2023-09-28 11:22:58 -06:00
2023-10-16 17:25:10 -04:00