40d70334e0
TL;DR podman needs "arm64" as arch, not "arm64v8". Unexpurgated version: docker.io publishes ${ARCH}/alpine for several values of ARCH. Unfortunately, the arm64 one is called "arm64v8", which is sensible, but podman needs the --arch value of the manifest to be exactly "arm64". So we need to special-case this value in our loop. Do so, and build/publish a new 20210610 testimage. Use that in tests moving forward. And, since we need to jump through the same hoops to build the nonlocal image, include it in the build loop instead of as a tacked-on comment. Try to be helpful by determining the next-available numeric tag. And: don't push anything by default. Instead, just tell the user what buildah-push commands to run. And: refactor $PODMAN_NONLOCAL_IMAGE_TAG, to make it easier for the RHEL-arch-testing folx to override using envariables instead of inplace-sed. (Not that they should ever need to override again, because this is the final multiarch commit that should be forevermore perfect and need no further commits ever again). And, finally, bump up to latest alpine/busybox images. Signed-off-by: Ed Santiago <santiago@redhat.com> |
||
---|---|---|
.. | ||
000-TEMPLATE | ||
001-basic.bats | ||
005-info.bats | ||
010-images.bats | ||
015-help.bats | ||
020-tag.bats | ||
030-run.bats | ||
035-logs.bats | ||
037-runlabel.bats | ||
040-ps.bats | ||
045-start.bats | ||
050-stop.bats | ||
055-rm.bats | ||
060-mount.bats | ||
065-cp.bats | ||
070-build.bats | ||
075-exec.bats | ||
080-pause.bats | ||
090-events.bats | ||
110-history.bats | ||
120-load.bats | ||
130-kill.bats | ||
140-diff.bats | ||
150-login.bats | ||
160-volumes.bats | ||
170-run-userns.bats | ||
200-pod.bats | ||
220-healthcheck.bats | ||
250-systemd.bats | ||
255-auto-update.bats | ||
260-sdnotify.bats | ||
270-socket-activation.bats | ||
300-cli-parsing.bats | ||
320-system-df.bats | ||
330-corrupt-images.bats | ||
400-unprivileged-access.bats | ||
410-selinux.bats | ||
420-cgroups.bats | ||
450-interactive.bats | ||
500-networking.bats | ||
600-completion.bats | ||
700-play.bats | ||
build-testimage | ||
helpers.bash | ||
helpers.t | ||
README.md | ||
TODO.md |
Quick overview of podman system tests. The idea is to use BATS, but with a framework for making it easy to add new tests and to debug failures.
Quick Start
Look at 030-run.bats for a simple but packed example. This introduces the basic set of helper functions:
-
setup
(implicit) - resets container storage so there's one and only one (standard) image, and no running containers. -
parse_table
- you can define tables of inputs and expected results, then read those in awhile
loop. This makes it easy to add new tests. Because bash is not a programming language, the caller ofparse_table
sometimes needs to massage the returned values;015-run.bats
offers examples of how to deal with the more typical such issues. -
run_podman
- runs command defined in$PODMAN
(default: 'podman' but could also be './bin/podman' or 'podman-remote'), with a timeout. Checks its exit status. -
is
- compare actual vs expected output. Emits a useful diagnostic on failure. -
die
- output a properly-formatted message to stderr, and fail test -
skip_if_rootless
- if rootless, skip this test with a helpful message. -
skip_if_remote
- like the above, but skip if testingpodman-remote
-
random_string
- returns a pseudorandom alphanumeric string
Test files are of the form NNN-name.bats
where NNN is a three-digit
number. Please preserve this convention, it simplifies viewing the
directory and understanding test order. In particular, 00x
tests
should be reserved for a first-pass fail-fast subset of tests:
bats test/system/00*.bats || exit 1
bats test/system
...the goal being to provide quick feedback on catastrophic failures without having to wait for the entire test suite.
Running tests
To run the tests locally in your sandbox, you can use one of these methods:
- make;PODMAN=./bin/podman bats ./test/system/070-build.bats # runs just the specified test
- make;PODMAN=./bin/podman bats ./test/system # runs all
To test as root:
- $ PODMAN=./bin/podman sudo --preserve-env=PODMAN bats test/system
Analyzing test failures
The top priority for this scheme is to make it easy to diagnose
what went wrong. To that end, podman_run
always logs all invoked
commands, their output and exit codes. In a normal run you will never
see this, but BATS will display it on failure. The goal here is to
give you everything you need to diagnose without having to rerun tests.
The is
comparison function is designed to emit useful diagnostics,
in particular, the actual and expected strings. Please do not use
the horrible BATS standard of [ x = y ]
; that's nearly useless
for tracking down failures.
If the above are not enough to help you track down a failure:
Debugging tests
Some functions have dprint
statements. To see the output of these,
set PODMAN_TEST_DEBUG="funcname"
where funcname
is the name of
the function or perhaps just a substring.
Requirements
The jq
tool is needed for parsing JSON output.
Further Details
TBD. For now, look in helpers.bash; each helper function
has (what are intended to be) helpful header comments. For even more
examples, see and/or run helpers.t
; that's a regression test
and provides a thorough set of examples of how the helpers work.