Matthew Heon 3858fc1d01 Use runtime names instead of paths in E2E tests ...

My patches to fix `--runtime /usr/bin/crun` being allowed to use
a different version of the crun runtime revealed a problem: we
were actually relying on that exact behavior in our E2E tests. We
specified the runtime path as `/usr/bin/runc` for the Ubuntu
tests, but that didn't exist, so Podman was actively looking for
a different, usable runc binary and using that, instead of the
path we explicitly hardcoded. Fixing the bug broke this, and thus
broke the tests.

Instead of hard-coding OCI runtime paths, swap to just using the
runtime name, `runc` or `crun`, and letting Podman figure out
where the runtime lives - it's quite good at that. This should
un-break the tests and make them more durable.

Signed-off-by: Matthew Heon <matthew.heon@pm.me>

2020-10-20 09:20:33 -04:00

..

commit.go

Switch all references to github.com/containers/libpod -> podman

2020-07-28 08:23:45 -04:00

config.go

CI: force registry:2.6

2020-06-19 12:58:02 +02:00

endpoint_suite_test.go

default build without varlink tag

2020-05-29 14:38:33 -04:00

endpoint.go

Remove some unnecessary []byte to string conversions

2020-08-03 09:13:04 +02:00

exists_test.go

Switch all references to github.com/containers/libpod -> podman

2020-07-28 08:23:45 -04:00

pull_test.go

Switch all references to github.com/containers/libpod -> podman

2020-07-28 08:23:45 -04:00

setup.go

Use runtime names instead of paths in E2E tests

2020-10-20 09:20:33 -04:00

version_test.go

Switch all references to github.com/containers/libpod -> podman

2020-07-28 08:23:45 -04:00