From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: QEMU Summit Minutes 2023
Date: Wed, 29 Nov 2023 16:57:55 +0000 [thread overview]
Message-ID: <877cm08pkc.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAJSP0QVSe6MZOS=20d9NMkJOAwsXaFF3aOOxZFkzhT-XZogG-w@mail.gmail.com> (Stefan Hajnoczi's message of "Wed, 29 Nov 2023 10:53:00 -0500")
Stefan Hajnoczi <stefanha@gmail.com> writes:
> To give a picture of the state of the CI, I'd say it fails 80% of the
> time. Usually 2 or 3 of the tests fail randomly from a group of <10
> tests that commonly fail randomly.
Do you have a list anywhere?
>
> In order for the CI to be usable to submaintainers I think it should
> _pass_ at least 90% of the time.
>
> There is still some way to go but I think this goal is achievable in
> the next 2 or 3 months because the set of problematic tests is not
> that large.
>
> Stefan
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-11-29 17:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 13:21 QEMU Summit Minutes 2023 Peter Maydell
2023-08-17 6:13 ` Thomas Huth
2023-11-21 17:11 ` Alex Bennée
2023-11-28 17:54 ` Cédric Le Goater
2023-11-28 18:05 ` Peter Maydell
2023-11-28 18:09 ` Daniel P. Berrangé
2023-11-28 18:06 ` Daniel P. Berrangé
2023-11-29 14:21 ` Philippe Mathieu-Daudé
2023-11-29 15:45 ` Warner Losh
2023-11-29 15:47 ` Stefan Hajnoczi
2023-11-29 15:53 ` Stefan Hajnoczi
2023-11-29 16:46 ` Daniel P. Berrangé
2023-11-29 16:49 ` Stefan Hajnoczi
2023-11-29 16:57 ` Alex Bennée [this message]
2023-11-29 18:24 ` Stefan Hajnoczi
2023-11-29 15:50 ` Warner Losh
2023-11-29 16:49 ` Daniel P. Berrangé
2023-11-29 19:41 ` Peter Maydell
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=877cm08pkc.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.