From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH 0/3] iotests: Check for the possibility to create large files
Date: Tue, 03 Dec 2019 10:14:23 +0000 [thread overview]
Message-ID: <87o8wpbts0.fsf@linaro.org> (raw)
In-Reply-To: <20191202101631.10003-1-thuth@redhat.com>
Thomas Huth <thuth@redhat.com> writes:
> Travis recently added the possibility to test on ppc64le, arm64 and s390x
> hosts, too. However, the containers are very restricted there and do not
> allow the creation of large files, so that the tests 060 and 079 are
> currently failing there. So let's add some proper checks to these tests
> first.
These look good to me, do you want them to go via my testing/next or are
Kevin and Max going to take it via their tree?
>
> Thomas Huth (3):
> iotests: Provide a function for checking the creation of huge files
> iotests: Skip test 060 if it is not possible to create large files
> iotests: Skip test 079 if it is not possible to create large files
>
> tests/qemu-iotests/005 | 5 +----
> tests/qemu-iotests/060 | 3 +++
> tests/qemu-iotests/079 | 3 +++
> tests/qemu-iotests/220 | 6 ++----
> tests/qemu-iotests/common.rc | 10 ++++++++++
> 5 files changed, 19 insertions(+), 8 deletions(-)
--
Alex Bennée
next prev parent reply other threads:[~2019-12-03 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 10:16 [PATCH 0/3] iotests: Check for the possibility to create large files Thomas Huth
2019-12-02 10:16 ` [PATCH 1/3] iotests: Provide a function for checking the creation of huge files Thomas Huth
2019-12-03 10:09 ` Alex Bennée
2019-12-02 10:16 ` [PATCH 2/3] iotests: Skip test 060 if it is not possible to create large files Thomas Huth
2019-12-02 10:16 ` [PATCH 3/3] iotests: Skip test 079 " Thomas Huth
2019-12-03 10:14 ` Alex Bennée [this message]
2019-12-09 13:32 ` [PATCH 0/3] iotests: Check for the possibility " Kevin Wolf
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=87o8wpbts0.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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 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.