From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Cédric Le Goater" <clg@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
"Thomas Huth" <thuth@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Steven Lee" <steven_lee@aspeedtech.com>,
"Troy Lee" <leetroy@gmail.com>,
"Jamin Lin" <jamin_lin@aspeedtech.com>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Joel Stanley" <joel@jms.id.au>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v2 1/4] tests/functional: Introduce _console_read()
Date: Tue, 12 Nov 2024 14:02:02 +0000 [thread overview]
Message-ID: <ZzNf2imfxQ3QF4qc@redhat.com> (raw)
In-Reply-To: <20241112130246.970281-2-clg@redhat.com>
On Tue, Nov 12, 2024 at 02:02:43PM +0100, Cédric Le Goater wrote:
> Interaction with the console has been a problem in our avocado
> tests. In some cases, the expected string does not match in the
> output, causing the test to fail with a timeout. These were worked
> around by sleeping before reading the console and even with SSH
> connections in some places.
>
> To fix, process the console output char by char and not with
> readline. This routine was largely inspired by console_wait() in
> tests/vm/basevm.py.
>
> Signed-off-by: Cédric Le Goater <clg@redhat.com>
> ---
> tests/functional/qemu_test/cmd.py | 22 ++++++++++++++++++++--
> 1 file changed, 20 insertions(+), 2 deletions(-)
>
> diff --git a/tests/functional/qemu_test/cmd.py b/tests/functional/qemu_test/cmd.py
> index cbabb1ceed3c..5bca29d1d721 100644
> --- a/tests/functional/qemu_test/cmd.py
> +++ b/tests/functional/qemu_test/cmd.py
> @@ -12,6 +12,7 @@
> # later. See the COPYING file in the top-level directory.
>
> import logging
> +import re
> import os
> import os.path
> import subprocess
> @@ -78,6 +79,23 @@ def run_cmd(args):
> def is_readable_executable_file(path):
> return os.path.isfile(path) and os.access(path, os.R_OK | os.X_OK)
>
> +def _console_read(vm, expect):
> + console_logger = logging.getLogger('console')
> + output = ""
> + while True:
> + data = vm.console_socket.recv(1)
> + if not data:
> + break
> + output += data.decode("latin1")
Decoding this as 'latin1' is going to mangle any output
that is not represented by a single-byte UTF-8 codepoint.
You can't simply switch this to 'utf8' though, as in the
socket.recv(1) call you're only reading a single byte,
and you can't guarantee that can be decoded if its part
of a multi-byte sequence.
I think you need to read into a bytearray, instead of
reading into a string. Then convert 'expect' into a
bytearray too, and compare bytes for a match, thus
avoiding problem of partial utf8 sequence decoding
errors.
> + if expect in output:
> + break
> + if "\r" in output or "\n" in output:
> + lines = re.split("[\r\n]", output)
> + if lines[0]:
> + console_logger.debug(lines[0])
> + output = lines.pop()
> + return output
In the commit message you talk about a problem with non-matched
text, and timeouts causing failure.
IIUC, the key difference between this code and the use of readline()
is that this code is checking for a match in the partial line. ie we
don't need to wait for a newline to arrive anymore.
That's an interesting difference, but its not obviously correlated
with the commit message description.
> +
> def _console_interaction(test, success_message, failure_message,
> send_string, keep_sending=False, vm=None):
> assert not keep_sending or send_string
> @@ -98,12 +116,12 @@ def _console_interaction(test, success_message, failure_message,
> continue
>
> try:
> - msg = console.readline().decode().strip()
> + msg = _console_read(vm, success_message)
> except UnicodeDecodeError:
> msg = None
> if not msg:
> continue
> - console_logger.debug(msg)
> + console_logger.debug('found "%s"', msg)
> if success_message is None or success_message in msg:
> break
> if failure_message and failure_message in msg:
> --
> 2.47.0
>
>
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:[~2024-11-12 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 13:02 [PATCH v2 0/4] tests/functional: Finish conversion of Aspeed tests Cédric Le Goater
2024-11-12 13:02 ` [PATCH v2 1/4] tests/functional: Introduce _console_read() Cédric Le Goater
2024-11-12 13:45 ` Thomas Huth
2024-11-12 13:52 ` Cédric Le Goater
2024-11-12 13:59 ` Thomas Huth
2024-11-12 14:02 ` Daniel P. Berrangé [this message]
2024-11-12 13:02 ` [PATCH v2 2/4] tests/functional: Convert Aspeed aarch64 SDK tests Cédric Le Goater
2024-11-12 13:02 ` [PATCH v2 3/4] tests/functional: Convert Aspeed arm " Cédric Le Goater
2024-11-12 13:58 ` Thomas Huth
2024-11-12 13:02 ` [PATCH v2 4/4] tests/functional: Remove sleep workarounds from Aspeed tests Cédric Le Goater
2024-11-12 13:36 ` Thomas Huth
2024-11-12 13:46 ` Cédric Le Goater
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=ZzNf2imfxQ3QF4qc@redhat.com \
--to=berrange@redhat.com \
--cc=andrew@codeconstruct.com.au \
--cc=clg@redhat.com \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=leetroy@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=steven_lee@aspeedtech.com \
--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 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.