On Sat, Jan 6, 2024 at 12:11 AM Peter Maydell <peter.mayd...@linaro.org> wrote: > > The avocado test acpiBitsTest.test_acpi_smbios_bits seems to be > flaky in CI -- sometimes it appears to time out. > > https://gitlab.com/qemu-project/qemu/-/issues/2077 > has the details (including links to jobs etc).
Do you have more data points in terms of the jobs that failed? The one you point to seems to be stuck in SMI latency tests: ==== SMI latency test ==== 16:45:49 DEBUG| Warning: touching the keyboard can affect the results of this test. 16:45:50 DEBUG| Starting test. Wait here, I will be back in 15 seconds. If this is consistently timing out here, we can disable the smi latency test. This test was a little problematic from the get go. Meanwhile I have assigned https://gitlab.com/qemu-project/qemu/-/issues/2077 to myself and will take a look. > As far as I can > see, the test is still running when after about a minute it > gets timed out. (Though the python tracebacks in the logs are > not easy for me to interpret, so I might be wrong). This I find > a bit confusing, because tests/avocado/acpi-bits.py sets > "timeout = 200". So maybe that isn't taking effect properly? > > Does anybody have time to investigate this? If not, we can disable > the test as flaky until somebody does have the time. > > thanks > -- PMM >
