From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: "Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] tests/boot-serial: Do not delete the output file in case of errors
Date: Wed, 27 Jun 2018 12:16:41 +0200 [thread overview]
Message-ID: <f5537d6c-b213-b982-0a63-1c9c397f807e@redhat.com> (raw)
In-Reply-To: <1526977831-31129-1-git-send-email-thuth@redhat.com>
On 22.05.2018 10:30, Thomas Huth wrote:
> Peter reported that the boot-serial tester sometimes runs into timeouts
> with SPARC guests. It's currently completely unclear whether this is due
> to too much load on the host machine (so that the guest really just ran
> too slow), or whether there is something wrong with the guest's firmware
> boot. For further debugging, we need the serial output of the guest in
> case of errors, so instead of unlinking the file immediately, this is
> now only done in case of success. In case of error, print the name of the
> file with the serial output via g_error() (which then also calls abort()
> internally to mark the test as failed).
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tests/boot-serial-test.c | 17 +++++++++--------
> 1 file changed, 9 insertions(+), 8 deletions(-)
Ping!
Paolo, could you take this patch through your misc / character devices
tree, please?
Thanks,
Thomas
next prev parent reply other threads:[~2018-06-27 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 8:30 [Qemu-devel] [PATCH] tests/boot-serial: Do not delete the output file in case of errors Thomas Huth
2018-05-22 21:21 ` Mark Cave-Ayland
2018-05-23 4:29 ` Thomas Huth
2018-06-27 10:16 ` Thomas Huth [this message]
2018-06-28 10:38 ` Paolo Bonzini
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=f5537d6c-b213-b982-0a63-1c9c397f807e@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).