f9fe3ae5dd
The pasta_podman/bats test scrpt downloads and builds podman, then runs its pasta specific tests. Downloading from within a test case has some drawbacks: * It can be very tedious if you have poor connectivity to the server * It makes a test that's ostensibly for pasta itself dependent on the state of the github server * It precludes runnning the tests in an isolated network environment The same concerns largely apply to building podman too, because it's pretty common for Go builds to download dependencies themselves. Therefore move the download and build of podman from the test itself, to the Makefile where we prepare other test assets. To avoid cryptic failures if something went wrong with the build, make running the test dependent on having the built podman binary. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
12 lines
104 B
Text
12 lines
104 B
Text
test_logs/
|
|
mbuto/
|
|
podman/
|
|
*.img
|
|
QEMU_EFI.fd
|
|
*.qcow2
|
|
*.raw
|
|
*.raw.xz
|
|
*.bin
|
|
nstool
|
|
guest-key
|
|
guest-key.pub
|