From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, "Thomas Huth" <thuth@redhat.com>,
berrange@redhat.com, stefanb@linux.vnet.ibm.com,
"Alex Bennée" <alex.bennee@linaro.org>,
"Cornelia Huck" <cohuck@redhat.com>,
richard.henderson@linaro.org, f4bug@amsat.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"open list:S390 general arch..." <qemu-s390x@nongnu.org>,
cota@braap.org, stefanha@redhat.com, marcandre.lureau@redhat.com,
pbonzini@redhat.com, aurelien@aurel32.net
Subject: [PATCH v1 5/5] travis.yml: Test the s390-ccw build, too
Date: Fri, 7 Feb 2020 11:39:39 +0000 [thread overview]
Message-ID: <20200207113939.9247-6-alex.bennee@linaro.org> (raw)
In-Reply-To: <20200207113939.9247-1-alex.bennee@linaro.org>
From: Thomas Huth <thuth@redhat.com>
Since we can now use a s390x host on Travis, we can also build and
test the s390-ccw bios images there. For this we have to make sure
that roms/SLOF is checked out, too, and then move the generated *.img
files to the right location before running the tests.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20200206202543.7085-1-thuth@redhat.com>
---
.travis.yml | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/.travis.yml b/.travis.yml
index 6c0ec6cf69f..c0eeff9caa9 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -508,6 +508,16 @@ matrix:
env:
- TEST_CMD="make check check-tcg V=1"
- CONFIG="--disable-containers --target-list=${MAIN_SOFTMMU_TARGETS},s390x-linux-user"
+ script:
+ - ( cd ${SRC_DIR} ; git submodule update --init roms/SLOF )
+ - BUILD_RC=0 && make -j${JOBS} || BUILD_RC=$?
+ - |
+ if [ "$BUILD_RC" -eq 0 ] ; then
+ mv pc-bios/s390-ccw/*.img pc-bios/ ;
+ ${TEST_CMD} ;
+ else
+ $(exit $BUILD_RC);
+ fi
# Release builds
# The make-release script expect a QEMU version, so our tag must start with a 'v'.
--
2.20.1
next prev parent reply other threads:[~2020-02-07 11:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 11:39 [PATCH v1 0/5] testing/next (rcutorture and misc tweaks) Alex Bennée
2020-02-07 11:39 ` [PATCH v1 1/5] tests/tcg: include a skip runner for pauth3 with plugins Alex Bennée
2020-02-07 11:39 ` [PATCH v1 2/5] tests/rcutorture: update usage hint Alex Bennée
2020-02-12 20:46 ` Philippe Mathieu-Daudé
2020-02-07 11:39 ` [PATCH v1 3/5] tests/rcutorture: better document locking of stats Alex Bennée
2020-02-12 20:47 ` Philippe Mathieu-Daudé
2020-02-07 11:39 ` [PATCH v1 4/5] tests/rcutorture: mild documenting refactor of update thread Alex Bennée
2020-02-07 11:39 ` Alex Bennée [this message]
2020-02-12 20:48 ` [PATCH v1 5/5] travis.yml: Test the s390-ccw build, too Philippe Mathieu-Daudé
2020-02-13 8:34 ` Cornelia Huck
2020-02-12 19:42 ` [PATCH v1 0/5] testing/next (rcutorture and misc tweaks) Alex Bennée
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=20200207113939.9247-6-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=stefanha@redhat.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).