From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"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>, "John Snow" <jsnow@redhat.com>,
qemu-ppc@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH 3/3] tests/avocado: Enable reverse_debugging.py tests in gitlab CI
Date: Tue, 21 Nov 2023 09:14:58 +0000 [thread overview]
Message-ID: <ZVx1EkxpK1ZH-nDn@redhat.com> (raw)
In-Reply-To: <31850f05-7849-402d-b3ae-623e76b52953@redhat.com>
On Tue, Nov 21, 2023 at 09:56:24AM +0100, Thomas Huth wrote:
> On 17/11/2023 08.35, Nicholas Piggin wrote:
> > 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.
>
> ... and here it's failing again (current master branch):
>
> https://gitlab.com/thuth/qemu/-/jobs/5582657378#L404
>
> According to the debug.log in the artifacts, it's failing here:
>
> 08:28:32 DEBUG| [ 0.230392217,5] OPAL v7.0 starting...
>
> 08:28:32 DEBUG| [ 0.230674939,7] initial console log level: memory 7, driver 5
>
> 08:28:32 DEBUG| [ 0.231048494,6] CPU: P9 generation processor (max 4 threads/core)
>
> 08:28:32 DEBUG| [
> 08:28:32 DEBUG| [ 0.231412547,7] CPU: Boot CPU PIR is 0x0000 PVR is 0x004e1202
>
> 08:28:32 DEBUG| [
> 08:28:32 ERROR|
> 08:28:32 ERROR| Reproduced traceback from: /builds/thuth/qemu/build/pyvenv/lib64/python3.8/site-packages/avocado/core/test.py:770
> 08:28:32 ERROR| Traceback (most recent call last):
> 08:28:32 ERROR| File "/builds/thuth/qemu/build/tests/avocado/reverse_debugging.py", line 262, in test_ppc64_powernv
> 08:28:32 ERROR| self.reverse_debugging()
> 08:28:32 ERROR| File "/builds/thuth/qemu/build/tests/avocado/reverse_debugging.py", line 178, in reverse_debugging
> 08:28:32 ERROR| g.cmd(b'c')
> 08:28:32 ERROR| File "/builds/thuth/qemu/build/pyvenv/lib64/python3.8/site-packages/avocado/utils/gdb.py", line 783, in cmd
> 08:28:32 ERROR| response_payload = self.decode(result)
> 08:28:32 ERROR| File "/builds/thuth/qemu/build/pyvenv/lib64/python3.8/site-packages/avocado/utils/gdb.py", line 738, in decode
> 08:28:32 ERROR| raise InvalidPacketError
> 08:28:32 ERROR| avocado.utils.gdb.InvalidPacketError
> 08:28:32 ERROR|
> 08:28:32 DEBUG| Local variables:
> 08:28:32 DEBUG| -> self <class 'reverse_debugging.ReverseDebugging_ppc64'>: 79-tests/avocado/reverse_debugging.py:ReverseDebugging_ppc64.test_ppc64_powernv
> 08:28:32 DEBUG| Shutting down VM appliance; timeout=30
> 08:28:32 DEBUG| Attempting graceful termination
> 08:28:32 DEBUG| Closing console socket
> 08:28:32 DEBUG| Politely asking QEMU to terminate
>
> So unless someone has a clue how to fix that, I guess it's
> likely best to revert this enablement patch again...
A little further in the log we see
08:28:32 DEBUG| Politely asking QEMU to terminate
08:28:32 DEBUG| --> {
"execute": "quit"
}
08:28:32 DEBUG| <-- {
"timestamp": {
"seconds": 1700555312,
"microseconds": 86122
},
"event": "RESUME"
}
08:28:32 ERROR| Task.Reader: BrokenPipeError: [Errno 32] Broken pipe
With seeing a bad packet from GDB and seeing Broken pipe from QMP,
my impression is that the QEMU process is no longer present, most
likely it has SEGV'd I reckon.
IOW, I think we might well have a genuine bug here, not merely an
unreliable test suite.
None the less, unless someone can guess what the problem is, we'll
need to disable the test to get reliable CI.
A bug should be opened though with the CI logs.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-11-21 9:15 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
2023-11-21 8:56 ` Thomas Huth
2023-11-21 9:14 ` Daniel P. Berrangé [this message]
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=ZVx1EkxpK1ZH-nDn@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=anisinha@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=npiggin@gmail.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=stefanha@redhat.com \
--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).