On 6/26/23 15:05, Juan Quintela wrote:
The "full logs" are
https://gitlab.com/qemu-project/qemu/-/jobs/4527202764/artifacts/download?file_type=trace
Not useful. I was hoping that there is something like when one runs
./tests/qtest/migration-test
I thought I saw some patch today that to save more artifacts.
But the bottom line is that we don't emit enough stuff from any of our tests to debug them
from logs -- we're too used to using other methods.
And I don't understand what CFI is (and I don't rule out that
posibility) or I can't understand how checking indirect functions call
can make migration-test die without a single CFI error message?
CFI (control flow inspection/validation/somesuch) adds checking along call paths, which
may affect timing.
This is almost certainly some sort of race condition.
Do we have a way to run on that image:
./tests/qtest/migration-test
in a loop until it fails, and at least see what test is failing?
Not as is, no. You'd have to create a new CI job, and for that you'll need advice beyond
myself.
r~
