From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Christian Schoenebeck" <qemu_oss@crudebyte.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Greg Kurz" <groug@kaod.org>, "Max Reitz" <mreitz@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: QEMU policy for real file tests
Date: Thu, 17 Sep 2020 14:11:18 +0100 [thread overview]
Message-ID: <CAFEAcA8yTpHE2WaBL3B8fbQtetqmH5uXgCudtfHXuYuA+LpavQ@mail.gmail.com> (raw)
In-Reply-To: <a60c566c-986c-2534-3e8e-6a3ff23b9d00@redhat.com>
On Thu, 17 Sep 2020 at 14:04, Thomas Huth <thuth@redhat.com> wrote:
>
> On 17/09/2020 14.06, Christian Schoenebeck wrote:
> [...]
> > Final question: if at some later point one large file needs to be created for
> > some test case, is there some approximate size limit to stay below for not
> > causing issues with free CI cloud services?
>
> FWIW, I know that 4G is already too big for some containers on Travis,
> see commit 178d383f10e15f5e5a7.
Yes. Also "it's sparse" doesn't always help -- eg on OSX there is
no sparse-file support so a 4GB file really does take 4GB even
if it's mostly zeroes...
thanks
-- PMM
next prev parent reply other threads:[~2020-09-17 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 8:50 QEMU policy for real file tests Christian Schoenebeck
2020-09-17 9:26 ` Alex Bennée
2020-09-17 9:37 ` Daniel P. Berrangé
2020-09-17 9:55 ` Thomas Huth
2020-09-17 12:06 ` Christian Schoenebeck
2020-09-17 12:24 ` Daniel P. Berrangé
2020-09-17 12:40 ` Peter Maydell
2020-09-17 13:04 ` Thomas Huth
2020-09-17 13:11 ` Peter Maydell [this message]
2020-09-17 14:04 ` Christian Schoenebeck
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=CAFEAcA8yTpHE2WaBL3B8fbQtetqmH5uXgCudtfHXuYuA+LpavQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=groug@kaod.org \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--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 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).