diff options
author | Ed Santiago <santiago@redhat.com> | 2020-02-20 14:19:24 -0700 |
---|---|---|
committer | Ed Santiago <santiago@redhat.com> | 2020-02-20 14:56:02 -0700 |
commit | a1dcfd47a1a35d47c51c10cc644d70f177bfdc0f (patch) | |
tree | 8dac38172b0b2aab7deefe446d5781180a1c9d31 /completions | |
parent | 83a9b318e150e96ba381f2fdf0db9d979e0740f0 (diff) | |
download | podman-a1dcfd47a1a35d47c51c10cc644d70f177bfdc0f.tar.gz podman-a1dcfd47a1a35d47c51c10cc644d70f177bfdc0f.tar.bz2 podman-a1dcfd47a1a35d47c51c10cc644d70f177bfdc0f.zip |
Flake fix: race condition in same-IP test
The "create two containers with the same IP" test failed:
https://api.cirrus-ci.com/v1/task/5992323062431744/logs/integration_test.log#t--Podman-create-two-containers-with-the-same-IP
...
(basically, expected error exit code, got 0)
Analysis: the sequence is 'start test1, start test2'. Perhaps it's
possible that 'podman start' exits before the test1 container has
an IP address assigned? There are no checks in the test, so it's
impossible to know what happened.
Solution: add a wait-loop invoking 'podman inspect', waiting
for a nonempty IP address on test 1; then assert that it's
what we expect it to be.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Diffstat (limited to 'completions')
0 files changed, 0 insertions, 0 deletions