From: Fam Zheng <famz@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 00/12] curl: fix curl read
Date: Tue, 28 May 2013 16:52:19 +0800 [thread overview]
Message-ID: <20130528085219.GB16648@localhost.nay.redhat.com> (raw)
In-Reply-To: <20130528084614.GA4889@redhat.com>
On Tue, 05/28 09:46, Richard W.M. Jones wrote:
> On Tue, May 28, 2013 at 08:47:59AM +0100, Richard W.M. Jones wrote:
> > I'm not sure if a Windows guest is somehow necessary to show the
> > errors. I'll retest with a Linux guest and get back to you about
> > that.
>
> Reproducible with Linux guest (remotely over slow Wifi).
>
> > Also I'm testing against a remote Apache2 server over a very slow Wifi
> > connection. Whereas your test was against localhost. Again, I will
> > test this scenario to see if that makes a difference and get back to
> > you.
>
> NOT reproducible with Windows XP guest over localhost, Apache2 server.
>
> So it seems to have something to do with the long latency and/or low
> bandwidth of the slow wifi connection here.
>
> I will add: This bug is not 100% reproducible on every run. However
> it does occur very frequently, probably in 9 out of 10 runs for me.
>
> Rich.
>
OK, I'll try a remote image then.
--
Fam
next prev parent reply other threads:[~2013-05-28 8:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 5:36 [Qemu-devel] [PATCH v6 00/12] curl: fix curl read Fam Zheng
2013-05-24 5:36 ` [Qemu-devel] [PATCH v6 01/12] curl: introduce CURLSockInfo to BDRVCURLState Fam Zheng
2013-05-24 5:36 ` [Qemu-devel] [PATCH v6 02/12] curl: change magic number to sizeof Fam Zheng
2013-05-24 5:36 ` [Qemu-devel] [PATCH v6 03/12] curl: change curl_multi_do to curl_fd_handler Fam Zheng
2013-05-24 5:36 ` [Qemu-devel] [PATCH v6 04/12] curl: fix curl_open Fam Zheng
2013-05-24 5:37 ` [Qemu-devel] [PATCH v6 05/12] curl: add timer to BDRVCURLState Fam Zheng
2013-05-24 5:37 ` [Qemu-devel] [PATCH v6 06/12] curl: introduce CURLDataCache Fam Zheng
2013-05-24 5:37 ` [Qemu-devel] [PATCH v6 07/12] curl: make use of CURLDataCache Fam Zheng
2013-05-24 5:37 ` [Qemu-devel] [PATCH v6 08/12] curl: use list to store CURLState Fam Zheng
2013-05-24 5:37 ` [Qemu-devel] [PATCH v6 09/12] curl: add cache quota Fam Zheng
2013-05-24 5:37 ` [Qemu-devel] [PATCH v6 10/12] curl: introduce ssl_no_cert runtime option Fam Zheng
2013-05-24 5:37 ` [Qemu-devel] [PATCH v6 11/12] block/curl.c: Refuse to open the handle for writes Fam Zheng
2013-05-24 5:37 ` [Qemu-devel] [PATCH v6 12/12] curl: set s->url to NULL after free Fam Zheng
2013-05-24 8:07 ` [Qemu-devel] [PATCH v6 00/12] curl: fix curl read Richard W.M. Jones
2013-05-27 2:25 ` Fam Zheng
2013-05-27 11:57 ` Richard W.M. Jones
2013-05-28 7:30 ` Fam Zheng
2013-05-28 7:47 ` Richard W.M. Jones
2013-05-28 8:46 ` Richard W.M. Jones
2013-05-28 8:52 ` Fam Zheng [this message]
2013-05-28 8:53 ` Richard W.M. Jones
2013-05-28 10:35 ` Richard W.M. Jones
2013-05-28 11:01 ` Richard W.M. Jones
2013-05-28 11:14 ` Fam Zheng
2013-05-28 11:25 ` Richard W.M. Jones
2013-05-28 11:32 ` Richard W.M. Jones
2013-05-29 1:07 ` Fam Zheng
2013-05-29 9:25 ` Richard W.M. Jones
2013-05-28 11:34 ` Stefan Hajnoczi
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=20130528085219.GB16648@localhost.nay.redhat.com \
--to=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=stefanha@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 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).