<feed xmlns='http://www.w3.org/2005/Atom'>
<title>packages/utils/oci-runtime-tools/test.sh, branch master</title>
<subtitle>Mirror of packages feed</subtitle>
<id>https://git.openwrt.org/feed/packages/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/feed/packages/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/'/>
<updated>2026-08-23T22:37:55Z</updated>
<entry>
<title>oci-runtime-tools: skip the version check for oci-runtime-tests</title>
<updated>2026-08-23T22:37:55Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2026-08-23T20:06:40Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=5117f9b2a4847a264935925086433cf52d840b79'/>
<id>urn:sha1:5117f9b2a4847a264935925086433cf52d840b79</id>
<content type='text'>
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 &lt;daniel@makrotopia.org&gt;
</content>
</entry>
</feed>
