You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a libvirt test (to check it is still okay after the CI hasn't been working for ~2 weeks 😢). I was hitting an issue about KBS image propertie not being provided:
# make test-e2e
go test -v -tags=libvirt -timeout 50m -count=1 ./test/e2e
time="2024-03-05T14:42:01Z" level=info msg="Do setup"
F0305 14:42:01.840056 24072 env.go:369] Setup failure: kbs image not provided
FAIL github.com/confidential-containers/cloud-api-adaptor/test/e2e 0.041s
FAIL
make: *** [Makefile:95: test-e2e] Error 1
However I didn't set DEPLOY_KBS=yes, so I don't think is should be needed.
I guess this shows the importance of those CI checks!
The text was updated successfully, but these errors were encountered:
Skip the kbs image property if we aren't deploying the KBS in the tests
Fixes: confidential-containers#1724
Signed-off-by: stevenhorsman <steven@uk.ibm.com>
FYI I've added #1726 to port Magnus' mkosi fix into packer, to hopefully fix the podvm issue and had my kcli PR merged, so hopefully we are getting closer to having working CI again!
When running a libvirt test (to check it is still okay after the CI hasn't been working for ~2 weeks 😢). I was hitting an issue about KBS image propertie not being provided:
However I didn't set
DEPLOY_KBS=yes
, so I don't think is should be needed.I guess this shows the importance of those CI checks!
The text was updated successfully, but these errors were encountered: