On 29/03/2023 21.11, Sean Christopherson wrote:
On Wed, Mar 29, 2023, Thomas Huth wrote:
Hi,
I noticed that in recent builds, the "memory" test started failing in the
kvm-unit-test CI. After doing some experiments, I think it might rather be
related to the environment than to a recent change in the k-u-t sources.
It used to work fine with commit 2480430a here in January:
https://gitlab.com/kvm-unit-tests/kvm-unit-tests/-/jobs/3613156199#L2873
Now I've re-run the CI with the same commit 2480430a here and it is failing now:
https://gitlab.com/thuth/kvm-unit-tests/-/jobs/4022074711#L2733
Can you provide the logs from the failing test, and/or the build artifacts? I
tried, and failed, to find them on Gitlab.
Yes, that's still missing in the CI scripts ... I'll try to come up with a
patch that provides the logs as artifacts.
Meanwhile, here's a run with a manual "cat logs/memory.log":
https://gitlab.com/thuth/kvm-unit-tests/-/jobs/4029213352#L2726
Seems like these are the failing memory tests:
FAIL: clflushopt (ABSENT)
FAIL: clwb (ABSENT)
Thomas
Does anybody have an idea what could be causing this regression? The build
in January used 7.0.0-12.fc37, the new build used 7.0.0-15.fc37, could that
be related? Or maybe a different kernel version?
Nothing jumps to mind. Triaging this without at least the logs in going to be
painful.
