From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Ying Fang <fangying1@huawei.com>
Cc: kwolf@redhat.com, zhang.zhanghailiang@huawei.com,
qemu-block@nongnu.org, qemu-devel@nongnu.org, mreitz@redhat.com,
alex.chen@huawei.com
Subject: Re: [PATCH] qcow2: flush qcow2 l2 meta for new allocated clusters
Date: Thu, 6 Aug 2020 10:04:12 +0100 [thread overview]
Message-ID: <20200806090412.GC4159383@redhat.com> (raw)
In-Reply-To: <6239531a-08d8-e538-30ac-ee58fef77aec@huawei.com>
On Thu, Aug 06, 2020 at 05:01:51PM +0800, Ying Fang wrote:
>
>
> On 8/5/2020 10:43 AM, no-reply@patchew.org wrote:
> > Patchew URL: https://patchew.org/QEMU/20200805023826.184-1-fangying1@huawei.com/
> >
> >
> >
> > Hi,
> >
> > This series failed the docker-quick@centos7 build test. Please find the testing commands and
> > their output below. If you have Docker installed, you can probably reproduce it
> > locally.
> > I see some error message which says ** No space left on device **
> However I do not know what is wrong with this build test.
> Could you give me some help here?
It isn't your fault - this is just QEMU's patchew CI that is broken yet again
due to lack of disk space. Just ignore the error report here.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-08-06 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 2:38 [PATCH] qcow2: flush qcow2 l2 meta for new allocated clusters Ying Fang
2020-08-05 2:43 ` no-reply
2020-08-06 9:01 ` Ying Fang
2020-08-06 9:04 ` Daniel P. Berrangé [this message]
2020-08-06 9:13 ` Kevin Wolf
2020-08-07 7:42 ` Ying Fang
2020-08-07 8:13 ` Kevin Wolf
2020-08-14 2:26 ` Ying Fang
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=20200806090412.GC4159383@redhat.com \
--to=berrange@redhat.com \
--cc=alex.chen@huawei.com \
--cc=fangying1@huawei.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=zhang.zhanghailiang@huawei.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.