Files
Ed Santiago ae5ed6d851 e2e create same-IP: try to fix flake
Our friend #7096 is still not fixed: it continues to flake,
singletons only, and only in the "create" test (not "run").

My guess: maybe there's a race somewhere in IP assignment,
such that container1 can have an IP, but not yet be running,
and a container2 can sneak in and start with that IP, and
container1 is the one that fails?

Solution: tighten the logic so we wait for container1 to
truly be running before we start container2. And, when we
start container2, do so with -a so we get to see stdout.
(Am not expecting it to be helpful, but who knows).

Also very minor cleanup

Signed-off-by: Ed Santiago <santiago@redhat.com>
2023-04-24 14:09:52 -06:00
..
2022-01-18 12:47:07 +01:00
2022-09-20 15:34:27 -04:00
2022-04-29 14:06:38 +02:00
2022-08-02 18:28:37 +09:00
2022-04-26 18:12:22 +02:00
2022-01-18 12:47:07 +01:00
2022-01-18 12:47:07 +01:00
2022-04-29 14:06:38 +02:00
2022-07-05 10:32:49 -04:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00
2023-01-06 08:21:50 -07:00
2022-09-20 15:34:27 -04:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00
2023-03-23 15:16:57 +01:00
2023-03-11 12:15:38 +01:00
2022-04-29 14:06:38 +02:00
2023-04-03 15:33:50 +03:00
2022-01-18 12:47:07 +01:00
2022-10-14 17:28:15 +02:00
2022-09-20 15:34:27 -04:00
2023-02-08 18:07:41 +09:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00
2022-04-29 14:06:38 +02:00