From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
"Max Reitz" <mreitz@redhat.com>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH 0/6] Enable Travis builds on arm64, ppc64le and s390x
Date: Fri, 22 Nov 2019 23:09:16 +0000 [thread overview]
Message-ID: <87wobr7bkz.fsf@linaro.org> (raw)
In-Reply-To: <20191119170822.45649-1-thuth@redhat.com>
Thomas Huth <thuth@redhat.com> writes:
> Travis recently added build hosts for arm64, ppc64le and s390x, so
> this is a welcome addition to our Travis testing matrix.
>
> Unfortunately, the builds are running in quite restricted LXD containers
> there, for example it is not possible to create huge files there (even
> if they are just sparse), and certain system calls are blocked. So we
> have to change some tests first to stop them failing in such environments.
<snip>
> 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
It seems like 161 is also failing:
https://travis-ci.org/stsquad/qemu/jobs/615672478
> tests/hd-geo-test: Skip test when images can not be created
> tests/test-util-filemonitor: Skip test on non-x86 Travis containers
> travis.yml: Enable builds on arm64, ppc64le and s390x
>
> .travis.yml | 85 ++++++++++++++++++++++++++++++++++-
> tests/hd-geo-test.c | 12 ++++-
> tests/qemu-iotests/060 | 6 +++
> tests/qemu-iotests/079 | 6 +++
> tests/test-util-filemonitor.c | 11 +++++
> 5 files changed, 118 insertions(+), 2 deletions(-)
--
Alex Bennée
next prev parent reply other threads:[~2019-11-22 23:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 17:08 [PATCH 0/6] Enable Travis builds on arm64, ppc64le and s390x Thomas Huth
2019-11-19 17:08 ` [PATCH 1/6] iotests: Skip test 060 if it is not possible to create large files Thomas Huth
2019-11-22 12:53 ` Alex Bennée
2019-11-19 17:08 ` [PATCH 2/6] iotests: Skip test 079 " Thomas Huth
2019-11-19 17:29 ` Philippe Mathieu-Daudé
2019-11-19 17:34 ` Thomas Huth
2019-11-19 17:38 ` Philippe Mathieu-Daudé
2019-11-19 17:50 ` Daniel P. Berrangé
2019-11-19 18:32 ` Thomas Huth
2019-11-22 12:57 ` Alex Bennée
2019-11-19 17:08 ` [PATCH 3/6] tests/hd-geo-test: Skip test when images can not be created Thomas Huth
2019-11-19 17:28 ` Philippe Mathieu-Daudé
2019-11-22 16:28 ` Alex Bennée
2019-11-19 17:08 ` [PATCH 4/6] tests/test-util-filemonitor: Skip test on non-x86 Travis containers Thomas Huth
2019-11-19 17:31 ` Philippe Mathieu-Daudé
2019-11-22 16:29 ` Alex Bennée
2019-11-19 17:08 ` [PATCH 5/6] travis.yml: drop 32 bit systems from MAIN_SOFTMMU_TARGETS Thomas Huth
2019-11-19 17:31 ` Philippe Mathieu-Daudé
2019-11-19 17:08 ` [PATCH 6/6] travis.yml: Enable builds on arm64, ppc64le and s390x Thomas Huth
2019-11-22 18:11 ` Alex Bennée
2019-11-22 23:09 ` Alex Bennée [this message]
2019-11-25 10:28 ` [PATCH 0/6] Enable Travis " Alex Bennée
2019-11-27 8:50 ` Thomas Huth
2019-12-04 14:03 ` Thomas Huth
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=87wobr7bkz.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@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.