oci-runtime-tools: skip the version check for oci-runtime-tests

runtimetest and the ~60 validation/*.go binaries oci-runtime-tests
installs are OCI compliance tests, not user-facing tools, and none
of them has a version flag. Probing one runs the test it implements
instead: CI's generic check reported 58 of 60 missing the version
string and failed the build, and the one it did run tried to read
rootfs-386.tar.gz relative to the probe's working directory rather
than /usr/libexec/oci-runtime-test, so it also failed outright.

Add a test.sh: skip oci-runtime-tests outright, since none of its
binaries can report a version, and keep the generic check for
oci-runtime-tool by replicating it directly now that --version
reports the right string.

Signed-off-by: Daniel Golle <redacted>

diff --git a/utils/oci-runtime-tools/test.sh b/utils/oci-runtime-tools/test.sh
new file mode 100755 (executable)
index 0000000..02ce6c9
--- /dev/null
+++ b/utils/oci-runtime-tools/test.sh
@@ -0,0 +1,19 @@
+#!/bin/sh
+
+case "$1" in
+oci-runtime-tool)
+       oci-runtime-tool --version 2>&1 | grep -F "$2"
+       ;;
+
+oci-runtime-tests)
+       # runtimetest and the validation/*.go test binaries installed here have
+       # no version flag; probing any of them with one runs the OCI compliance
+       # test it implements instead, out of the working directory it expects
+       exit 0
+       ;;
+
+*)
+       echo "Untested package: $1" >&2
+       exit 1
+       ;;
+esac