On Sat, Jan 6, 2024 at 5:39 PM Peter Maydell <peter.mayd...@linaro.org> wrote: > > On Sat, 6 Jan 2024 at 05:41, Ani Sinha <anisi...@redhat.com> wrote: > > > > On Sat, Jan 6, 2024 at 10:05 AM Ani Sinha <anisi...@redhat.com> wrote: > > > > > > 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? > > > > I just noticed that you attached three examples of failed tests. In > > all of them the test seems to be stuck at the ami latency test. > > OK, if you think that subtest is suspicious, could you send a > patch that disables just that subpart, and we'll see if it helps?
I pushed the patches here: https://gitlab.com/anisinha/qemu/-/commits/disable-smilatency and ran the pipeline. It passed https://gitlab.com/anisinha/qemu/-/jobs/5878585312 and the smilatency test was not run: https://anisinha.gitlab.io/-/qemu/-/jobs/5878585312/artifacts/build/tests/results/latest/test-results/01-tests_avocado_acpi-bits.py_AcpiBitsTest.test_acpi_smbios_bits/debug.log Not sure what we can do to have some confidence that disabling the test got rid of the flakiness. I can send out those two patches in the list.
