Cirrus: Fix c/image CI testing

The containers/image CI setup reuses the runner script from this repo to
execute the skopeo tests.  However, an env. var. is being taken out of
context in that environment, leading to failure.  Fix this by
hard-coding an image-name which will always be available in both
environments.

Signed-off-by: Chris Evich <cevich@redhat.com>
This commit is contained in:
Chris Evich 2023-01-19 12:34:03 -05:00
parent 9d65de7d61
commit 67a8bef6ea
No known key found for this signature in database
GPG Key ID: 03EDC70FD578067F

View File

@ -115,19 +115,15 @@ _run_unit() {
_podman_reset() { _podman_reset() {
# Ensure we start with a clean-slate # Ensure we start with a clean-slate
showrun podman system reset --force showrun podman system reset --force
# Don't pollute the CI environment # WARNING WARNING WARNING WARNING
( # Without running a container, the system tests will inexplicably
source $CIRRUS_WORKING_DIR/systemtest/helpers.bash # fail with obscure errors/warning messages. I have no idea why
# WARNING WARNING WARNING WARNING # running a container after a `system reset` fixes/prevents the
# Without running a container, the system tests will inexplicably # problem. The failures do not reproduce when tests are run manually.
# fail with obscure errors/warning messages. I have no idea why # So unless or until /until somebody develops a better understanding,
# running a container after a `system reset` fixes/prevents the # this fix is JFM - just fakking magic.
# problem. The failures do not reproduce when tests are run manually. # WARNING WARNING WARNING WARNING
# So unless or until /until somebody develops a better understanding, showrun podman run -it --rm --entrypoint /bin/true quay.io/libpod/alpine:latest
# this fix is JFM.
# WARNING WARNING WARNING WARNING
showrun podman run -it --rm --entrypoint /bin/true $REGISTRY_FQIN
)
} }
_run_integration() { _run_integration() {