From: Peter Maydell <peter.maydell@linaro.org>
To: Ani Sinha <anisinha@redhat.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Phil Mathieu-Daudé" <philmd@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: acpiBitsTest.test_acpi_smbios_bits test intermittently times out
Date: Sat, 6 Jan 2024 12:09:17 +0000 [thread overview]
Message-ID: <CAFEAcA-fjZw9x2RC+Czo8dQUuux1WUD6fDWCMJ-1xHdGevNWAw@mail.gmail.com> (raw)
In-Reply-To: <CAK3XEhNe4TO4oBavsuqJwP5e1nzB6+xpdWa-D0NEq_-rqXincw@mail.gmail.com>
On Sat, 6 Jan 2024 at 05:41, Ani Sinha <anisinha@redhat.com> wrote:
>
> On Sat, Jan 6, 2024 at 10:05 AM Ani Sinha <anisinha@redhat.com> wrote:
> >
> > On Sat, Jan 6, 2024 at 12:11 AM Peter Maydell <peter.maydell@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?
Thanks for looking into the issue.
-- PMM
next prev parent reply other threads:[~2024-01-06 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 18:41 acpiBitsTest.test_acpi_smbios_bits test intermittently times out Peter Maydell
2024-01-06 4:35 ` Ani Sinha
2024-01-06 5:41 ` Ani Sinha
2024-01-06 12:09 ` Peter Maydell [this message]
2024-01-07 16:26 ` Ani Sinha
2024-01-08 10:38 ` Ani Sinha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFEAcA-fjZw9x2RC+Czo8dQUuux1WUD6fDWCMJ-1xHdGevNWAw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=anisinha@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).