diff options
| author | Aditya R <arajan@redhat.com> | 2022-03-14 15:36:32 +0530 |
|---|---|---|
| committer | Aditya R <arajan@redhat.com> | 2022-03-14 20:41:38 +0530 |
| commit | daebf50b899fe998b8866a9f99e4c2b677645091 (patch) | |
| tree | 44092015532e5529fc3cea397e1622f7b6dc812e /vendor/github.com/fsouza/go-dockerclient/event.go | |
| parent | c845216fdd1974e51efedbe5861da34d20c1763b (diff) | |
| download | podman-daebf50b899fe998b8866a9f99e4c2b677645091.tar.gz podman-daebf50b899fe998b8866a9f99e4c2b677645091.tar.bz2 podman-daebf50b899fe998b8866a9f99e4c2b677645091.zip | |
apply-podman-deltas: skip modified test case for --add-host which adds anomaly
All podman tests in CI expects exit code 125, which might not be true since exit code from runtime
is relayed as it is without any modification both in `buildah` and `podman`. Following behviour is seen when PR https://github.com/containers/buildah/pull/3809
added a test here https://github.com/containers/buildah/blob/main/tests/bud.bats#L3183 which relays exit code from runtime as it
is, in case of both `podman` and `buildah`. However apart from this test case no other test case was able to trigger this behviour hence
marking this test as an anomaly. Since its debatable if we should override this returned error number or not hence adding a note here.
Signed-off-by: Aditya R <arajan@redhat.com>
Diffstat (limited to 'vendor/github.com/fsouza/go-dockerclient/event.go')
0 files changed, 0 insertions, 0 deletions