From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Christian Borntraeger" <borntraeger@de.ibm.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Richard Henderson" <rth@twiddle.net>,
"Alexander Graf" <agraf@suse.de>,
"Cornelia Huck" <cornelia.huck@de.ibm.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] qemu-system-s390x tests/boot-serial-test intermittent failure
Date: Fri, 24 Mar 2017 11:37:14 +0000 [thread overview]
Message-ID: <CAFEAcA9H6vah+ogTsc+TYaZ_X=ncW9frCK5QYBvorN8rQ1EshA@mail.gmail.com> (raw)
In-Reply-To: <fcb69c2f-cee4-7acc-b396-0cfc193cff59@redhat.com>
On 24 March 2017 at 11:26, Thomas Huth <thuth@redhat.com> wrote:
> I was not able to reproduce this issue so far (on my x86 laptop since I
> don't have an aarch64 host) ... can you reproduce it by running the test
> directly, too, e.g. something like:
>
> QTEST_QEMU_BINARY=s390x-softmmu/qemu-system-s390x tests/boot-serial-test
>
> ?
Yes, you can.
>> Adding Thomas who did the s390 version.
>>
>> One idea. Maybe qemu exits before the other side is ready.
>
> Or could this be a timeout issue again? Is the host very loaded?
> (however, I don't really believe that this could be the issue here,
> since the test is rather fast)
The timeout is 60 seconds, right? When the test fails it
fails immediately, not after hanging for 60s.
thanks
-- PMM
next prev parent reply other threads:[~2017-03-24 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 10:57 [Qemu-devel] qemu-system-s390x tests/boot-serial-test intermittent failure Peter Maydell
2017-03-24 11:11 ` Christian Borntraeger
2017-03-24 11:26 ` Thomas Huth
2017-03-24 11:37 ` Peter Maydell [this message]
2017-03-24 11:48 ` Paolo Bonzini
2017-03-24 11:50 ` Peter Maydell
2017-03-24 12:56 ` Peter Maydell
2017-03-24 13:02 ` Christian Borntraeger
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='CAFEAcA9H6vah+ogTsc+TYaZ_X=ncW9frCK5QYBvorN8rQ1EshA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=alex.bennee@linaro.org \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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.