Open stevenhorsman opened 2 months ago
This is getting worse and we are hitting it multiple times on each PR now. I've tried running this test locally and in about 8 re-runs it worked every time, so I'm not sure of the cause of the failure. In the short term I think we need to skip it in the CI to stop it blocking PRs.
It is possible that this is related to the image-pull changes as Chengyu is touch the config merge code in https://github.com/kata-containers/kata-containers/pull/9695, so after this, we should try re-testing this.
Hmm, this is suspicious, now the e2e tests related to env are skipped I've seen:
=== RUN TestLibvirtCreatePeerPodAndCheckWorkDirLogs
=== RUN TestLibvirtCreatePeerPodAndCheckWorkDirLogs/WorkDirPeerPod_test
assessment_runner.go:262: timed out waiting for the condition
--- FAIL: TestLibvirtCreatePeerPodAndCheckWorkDirLogs (600.16s)
--- FAIL: TestLibvirtCreatePeerPodAndCheckWorkDirLogs/WorkDirPeerPod_test (600.16s)
start failing, so maybe it's related to something before now being cleaned up, or the workdir has the same issue?
We see occasional (anecdotally <20% of the time) failures on the libvirt nightly CI, which seems to always (so far) pass on re-run and now we've seen in on a PR test, so it's becoming more of an obstacle, so we should investigate it when we get the chance