From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: "Richard Henderson" <rth@twiddle.net>,
"Alexander Graf" <agraf@suse.de>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Cornelia Huck" <cornelia.huck@de.ibm.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] qemu-system-s390x tests/boot-serial-test intermittent failure
Date: Fri, 24 Mar 2017 10:57:00 +0000 [thread overview]
Message-ID: <CAFEAcA_sboyuxUo9b_WAc18Ov9ehfUnura7C5r5ZzfDmjd-XLw@mail.gmail.com> (raw)
Hi; qemu-system-s390x seems to have an intermittent failure at
the moment -- it's been causing our Travis builds to flap. I actually
caught it doing this on one of my local test builds (which happens
to be aarch64 but I don't think that matters, since Travis is doing
x86 builds):
while QTEST_QEMU_BINARY=s390x-softmmu/qemu-system-s390x
QTEST_QEMU_IMG=qemu-img MALLOC_PERTURB_=${MALLOC_PERTURB_:-$((RANDOM %
255 + 1))} gtester -k --verbose -m=quick tests/boot-serial-test ; do
true; done
TEST: tests/boot-serial-test... (pid=1122)
/s390x/boot-serial/s390-ccw-virtio: OK
PASS: tests/boot-serial-test
TEST: tests/boot-serial-test... (pid=1135)
/s390x/boot-serial/s390-ccw-virtio: OK
[skip lots more successes]
TEST: tests/boot-serial-test... (pid=1582)
/s390x/boot-serial/s390-ccw-virtio:
Broken pipe
FAIL
GTester: last random seed: R02Se94f36f305f2edd8391a22749ec91143
(pid=1635)
FAIL: tests/boot-serial-test
Any ideas?
thanks
-- PMM
next reply other threads:[~2017-03-24 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 10:57 Peter Maydell [this message]
2017-03-24 11:11 ` [Qemu-devel] qemu-system-s390x tests/boot-serial-test intermittent failure Christian Borntraeger
2017-03-24 11:26 ` Thomas Huth
2017-03-24 11:37 ` Peter Maydell
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=CAFEAcA_sboyuxUo9b_WAc18Ov9ehfUnura7C5r5ZzfDmjd-XLw@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 \
/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.