From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Pavel Dovgalyuk" <pavel.dovgaluk@ispras.ru>,
"Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Ani Sinha" <anisinha@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"John Snow" <jsnow@redhat.com>,
qemu-ppc@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 3/3] tests/avocado: Enable reverse_debugging.py tests in gitlab CI
Date: Fri, 17 Nov 2023 17:35:42 +1000 [thread overview]
Message-ID: <CX0WX30H69LM.3MYDJODZ4LQWF@wheely> (raw)
In-Reply-To: <24a194bc-81c6-44ae-9113-94ed28cc4f71@redhat.com>
On Fri Nov 17, 2023 at 4:11 AM AEST, Thomas Huth wrote:
> On 16/11/2023 12.53, Nicholas Piggin wrote:
> > Let's try enable reverse_debugging.py in gitlab CI.
> >
> > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> > ---
> > Maybe we could try this again at some point? The bug might have been
> > noticed sooner.
> >
> > They only take a couple of seconds to run so should not take too much
> > overhead. But my gitlab CI pipeline doesn't run the avocado tests for
> > some reason, so I can't see if it's still causing problems.
> >
> > Thanks,
> > Nick
> > ---
> >
> > tests/avocado/reverse_debugging.py | 7 -------
> > 1 file changed, 7 deletions(-)
>
> FYI, I gave it a try, and it survived my CI run:
>
> https://gitlab.com/thuth/qemu/-/jobs/5552213972#L403
>
> So I went ahead and put it (together with the first patch) in my current
> pull request, let's see how it goes...
Great, thank you.
> (for the second patch, I hope our chardev maintainer Marc-André could
> comment on that first)
Yeah that would be good, no rush for that one. Maybe it's not desirable
for other reasons too.
Thanks,
Nick
next prev parent reply other threads:[~2023-11-17 7:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 11:53 [PATCH 1/3] tests/avocado: reverse_debugging drain console to prevent hang Nicholas Piggin
2023-11-16 11:53 ` [PATCH 2/3] chardev: report blocked write to chardev backend Nicholas Piggin
2023-11-20 12:06 ` Marc-André Lureau
2023-11-20 13:35 ` Nicholas Piggin
2023-11-21 9:39 ` Marc-André Lureau
2023-11-21 9:42 ` Daniel P. Berrangé
2023-11-21 9:44 ` Thomas Huth
2023-11-21 11:47 ` Marc-André Lureau
2023-11-22 9:55 ` Alex Bennée
2023-11-22 10:38 ` Thomas Huth
2023-11-22 10:42 ` Daniel P. Berrangé
2023-11-16 11:53 ` [PATCH 3/3] tests/avocado: Enable reverse_debugging.py tests in gitlab CI Nicholas Piggin
2023-11-16 12:33 ` Thomas Huth
2023-11-16 18:11 ` Thomas Huth
2023-11-17 7:35 ` Nicholas Piggin [this message]
2023-11-21 8:56 ` Thomas Huth
2023-11-21 9:14 ` Daniel P. Berrangé
2023-11-21 9:40 ` Thomas Huth
2023-11-16 13:26 ` [PATCH 1/3] tests/avocado: reverse_debugging drain console to prevent hang Ani Sinha
2023-11-16 13:31 ` Ani Sinha
2023-11-16 13:39 ` 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=CX0WX30H69LM.3MYDJODZ4LQWF@wheely \
--to=npiggin@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=anisinha@redhat.com \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
--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).