From: Fam Zheng <famz@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL v2 0/3] Merge qio 2017/02/27
Date: Fri, 3 Mar 2017 21:24:44 +0800 [thread overview]
Message-ID: <20170303132444.GG7097@lemon.lan> (raw)
In-Reply-To: <6d02fcc5-f5e0-4f33-fe77-1a6b6f167b4a@de.ibm.com>
On Fri, 03/03 13:33, Christian Borntraeger wrote:
> On 03/03/2017 10:53 AM, Fam Zheng wrote:
> > On Fri, 03/03 09:12, Christian Borntraeger wrote:
> >> On 03/02/2017 05:33 PM, no-reply@patchew.org wrote:
> >>
> >> Fam, this seems to happen sometimes. Can you have a look at that why the qtest
> >> thing fails on the s390 box?
> >
> > I don't know, when I run the commands manually for a few times, it is not
> > reproduced. :(
>
> Just guessing, maybe you have two runs in parallel that use the same folder
> for some reason?
>
The reason to use a fixed temp dir is ccache. Next time such a failure shows up,
I'll switch to unique dir for each test run.
Fam
next prev parent reply other threads:[~2017-03-03 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 16:10 [Qemu-devel] [PULL v2 0/3] Merge qio 2017/02/27 Daniel P. Berrange
2017-03-02 16:10 ` [Qemu-devel] [PULL v2 1/3] io: fix decoding when multiple websockets frames arrive at once Daniel P. Berrange
2017-03-02 16:10 ` [Qemu-devel] [PULL v2 2/3] tests: fix leaks in test-io-channel-command Daniel P. Berrange
2017-03-02 16:10 ` [Qemu-devel] [PULL v2 3/3] io: fully parse & validate HTTP headers for websocket protocol handshake Daniel P. Berrange
2017-03-02 16:33 ` [Qemu-devel] [PULL v2 0/3] Merge qio 2017/02/27 no-reply
2017-03-03 8:12 ` Christian Borntraeger
2017-03-03 9:53 ` Fam Zheng
2017-03-03 12:33 ` Christian Borntraeger
2017-03-03 13:24 ` Fam Zheng [this message]
2017-03-03 13:22 ` Christian Borntraeger
2017-03-03 13:39 ` Fam Zheng
2017-03-03 14:04 ` Peter Maydell
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=20170303132444.GG7097@lemon.lan \
--to=famz@redhat.com \
--cc=borntraeger@de.ibm.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).