summaryrefslogtreecommitdiff
path: root/cni
diff options
context:
space:
mode:
authorAshley Cui <acui@redhat.com>2022-03-08 09:45:48 -0500
committerAshley Cui <acui@redhat.com>2022-03-08 10:05:42 -0500
commit9ce3c0a87a6d7da45e71719b2ceb6d6abb0433fe (patch)
treec25f7e6b7565c3d4993ba87d372e9678be55d079 /cni
parente1f00b451234fb673505c54051a97d5748c99d3e (diff)
downloadpodman-9ce3c0a87a6d7da45e71719b2ceb6d6abb0433fe.tar.gz
podman-9ce3c0a87a6d7da45e71719b2ceb6d6abb0433fe.tar.bz2
podman-9ce3c0a87a6d7da45e71719b2ceb6d6abb0433fe.zip
Move secret-verify-leak containerfile into its own Directory
Secret-verify-leak is causing flakes, when running in parallel tests. This is because remote secrets are copied into the context directory to send to the API server, and secret-verify-leak is doing a COPY * and then checking if the temporary secret file ends up in the container or not. Since all the temporary files are prefixed with "podman-build-secret", this test checks if podman-build-secret is in the image. However, when run in parallel with other tests, other temporary podman-build-secrets might be in the context dir. Moving secret-verify-leak into its own directory makes sure that the context dir is used only by this one test. Also renamed Dockerfile -> Containerfile and cleaned up unused Containerfiles. Signed-off-by: Ashley Cui <acui@redhat.com>
Diffstat (limited to 'cni')
0 files changed, 0 insertions, 0 deletions