containers
/
podman
mirror of https://github.com/containers/podman.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

hack/bats: improve usage message 

Signed-off-by: Ed Santiago <santiago@redhat.com>
This commit is contained in:
Ed Santiago 2023-01-04 14:01:52 -07:00
parent d7ac11005c
commit 710eeb3403
1 changed files with 13 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
hack/bats
View File

@ -29,20 +29,27 @@ $0 is a wrapper for invoking podman system tests.
By default, tests ./bin/podman. To test a different podman, do: By default, tests ./bin/podman. To test a different podman, do:
\$ PODMAN=/abs/path/to/podman $0 .... \$ env PODMAN=/abs/path/to/podman $0 ....
To test podman-remote, start your own servers (root and rootless) via: To test podman-remote, start your own servers (root and rootless) via:
\$ bin/podman system service --timeout=0 & \$ bin/podman system service --timeout=0 &
\$ sudo !! \$ sudo !!
...then invoke this script with --remote. ...then invoke this script with --remote. (This script can't start the
servers, because we can sudo *starting* the service but can't sudo
(This script cannot start the servers, because we can sudo *starting* stopping it: by the time the bats tests finish, the sudo timeout will
the service but can't sudo stopping it: by the time the bats tests have expired. We apologize for the inconvenience.)
finish, the sudo timeout will have expired.)
$0 also passes through \$OCI_RUNTIME, should you need to test that. $0 also passes through \$OCI_RUNTIME, should you need to test that.
Examples:
\$ $0 220:\"restart cleans up\"
... only the \"restart cleans up\" test in 220-healthcheck.bats
\$ $0 --root 160:\"ps -f\"
... runs all tests in 160-volumes.bats that match \"ps -f\" (root only)
" "
# END usage message # END usage message