From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH 4/6] tests/functional: drop datadrainer class in reverse debugging
Date: Mon, 15 Sep 2025 11:38:27 +0100 [thread overview]
Message-ID: <aMfso1ksrXgznBvi@redhat.com> (raw)
In-Reply-To: <878qigrpcu.fsf@draig.linaro.org>
On Mon, Sep 15, 2025 at 11:18:09AM +0100, Alex Bennée wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > The reverse debugging test uses the avocado datadrainer class to
> > create a background thread that reads from the console socket and
> > dumps it via python logger.
> >
> > Most tests log console output as a side effect of doing calls
> > to match strings, but this test never tries to match anything.
> >
> > This isn't critical, so just drop the functionality.
>
> We do end up with zero length logs for all console output although I don't know
> if we got that far before:
AFAICT, the logs were also zero-length with the current code.
When I ran it with the datadrainer code, there didn't seem
to be any output to be drained. I'm unclear if that's expected
or a sign I did something wrong, or something has broken since
the test was first written ?
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > tests/functional/reverse_debugging.py | 6 ------
> > 1 file changed, 6 deletions(-)
> >
> > diff --git a/tests/functional/reverse_debugging.py b/tests/functional/reverse_debugging.py
> > index 1b880cda8f..9c89f5c897 100644
> > --- a/tests/functional/reverse_debugging.py
> > +++ b/tests/functional/reverse_debugging.py
> > @@ -35,8 +35,6 @@ class ReverseDebugging(LinuxKernelTest):
> > endian_is_le = True
> >
> > def run_vm(self, record, shift, args, replay_path, image_path, port):
> > - from avocado.utils import datadrainer
> > -
> > logger = logging.getLogger('replay')
> > vm = self.get_vm(name='record' if record else 'replay')
> > vm.set_console()
> > @@ -54,10 +52,6 @@ def run_vm(self, record, shift, args, replay_path, image_path, port):
> > if args:
> > vm.add_args(*args)
> > vm.launch()
> > - console_drainer = datadrainer.LineLogger(vm.console_socket.fileno(),
> > - logger=self.log.getChild('console'),
> > - stop_check=(lambda : not vm.is_running()))
> > - console_drainer.start()
> > return vm
> >
> > @staticmethod
>
> --
> Alex Bennée
> Virtualisation Tech Lead @ Linaro
>
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:[~2025-09-15 10:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 18:21 [PATCH 0/6] tests/functional: remove last use of avocado.utils Daniel P. Berrangé
2025-09-12 18:21 ` [PATCH 1/6] tests/functional: import GDB remote code from avocado Daniel P. Berrangé
2025-09-15 10:06 ` Alex Bennée
2025-09-12 18:21 ` [PATCH 2/6] tests/functional: convert reverse debug test to local gdb module Daniel P. Berrangé
2025-09-15 10:06 ` Alex Bennée
2025-09-12 18:21 ` [PATCH 3/6] tests/functional: replace avocado process with subprocess Daniel P. Berrangé
2025-09-15 10:07 ` Alex Bennée
2025-09-12 18:21 ` [PATCH 4/6] tests/functional: drop datadrainer class in reverse debugging Daniel P. Berrangé
2025-09-15 10:18 ` Alex Bennée
2025-09-15 10:38 ` Daniel P. Berrangé [this message]
2025-09-15 12:04 ` Alex Bennée
2025-09-15 12:05 ` Alex Bennée
2025-09-12 18:21 ` [PATCH 5/6] tests/functional: close GDB socket in reverse debugging test Daniel P. Berrangé
2025-09-15 10:18 ` Alex Bennée
2025-09-12 18:22 ` [PATCH 6/6] tests/functional: use self.log for all logging Daniel P. Berrangé
2025-09-15 10:19 ` Alex Bennée
2025-09-15 10:39 ` Daniel P. Berrangé
2025-09-15 10:24 ` [PATCH 0/6] tests/functional: remove last use of avocado.utils Alex Bennée
2025-09-15 10:42 ` Daniel P. Berrangé
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=aMfso1ksrXgznBvi@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).