From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Stefan Weil" <sw@weilnetz.de>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
luoyonggang@gmail.com, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2 7/7] gitlab-ci: Add cross-compiling build tests
Date: Tue, 1 Sep 2020 18:36:45 +0200 [thread overview]
Message-ID: <a39b632a-5d59-0a63-b342-644f052ee1ff@redhat.com> (raw)
In-Reply-To: <20200901162743.GX345480@redhat.com>
On 01/09/2020 18.27, Daniel P. Berrangé wrote:
> On Sun, Aug 23, 2020 at 01:17:57PM +0200, Thomas Huth wrote:
>> Now that we can use all our QEMU test containers in the gitlab-CI, we can
>> easily add some jobs that test cross-compilation for various architectures.
>> There is just only small ugliness: Since the shared runners on gitlab.com
>> are single-threaded, we have to split each compilation job into two parts
>> (--disable-user and --disable-system), and exclude some additional targets,
>> to avoid that the jobs are running too long and hitting the timeout of 1 h.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> .gitlab-ci.d/crossbuilds.yml | 113 +++++++++++++++++++++++++++++++++++
>> .gitlab-ci.yml | 1 +
>> MAINTAINERS | 1 +
>> 3 files changed, 115 insertions(+)
>> create mode 100644 .gitlab-ci.d/crossbuilds.yml
>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>
>>
>> diff --git a/.gitlab-ci.d/crossbuilds.yml b/.gitlab-ci.d/crossbuilds.yml
>> new file mode 100644
>> index 0000000000..4ec7226b5c
>> --- /dev/null
>> +++ b/.gitlab-ci.d/crossbuilds.yml
>> @@ -0,0 +1,113 @@
>> +
>> +.cross_system_build_job_template: &cross_system_build_job_definition
>> + stage: build
>> + image: $CI_REGISTRY_IMAGE/qemu/$IMAGE:latest
>> + script:
>> + - mkdir build
>> + - cd build
>> + - PKG_CONFIG_PATH=$PKG_CONFIG_PATH
>> + ../configure --enable-werror $QEMU_CONFIGURE_OPTS --disable-user
>> + --target-list-exclude="aarch64-softmmu i386-softmmu microblaze-softmmu
>> + mips-softmmu mipsel-softmmu mips64-softmmu ppc64-softmmu sh4-softmmu
>> + xtensa-softmmu"
>
> What does this leave enabled ? Would it be shorter to just say
> --target-list="...explicit targets we want..." ? It would be clearer
> to review at least.
I basically excluded all targets that have a second compile test
coverage, e.g. i386-softmmu code is mostly also covered by
x86_64-softmmu, sh4-softmmu is covered by sh4eb-softmmu etc.
The --target-list-exclude also comes in handy when new targets are added
to QEMU - you then don't have to remember to add the new targets here,
they are picked up automatically.
>> + - make -j$(expr $(nproc) + 1) all check-build
>
> None the less, it is functionally fine so
>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Thanks!
Thomas
next prev parent reply other threads:[~2020-09-01 16:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 11:17 [PATCH v2 0/7] Run cross-compilation build tests in the gitlab-CI Thomas Huth
2020-08-23 11:17 ` [PATCH v2 1/7] configure: Add system = 'linux' for meson when cross-compiling Thomas Huth
2020-09-01 16:18 ` Daniel P. Berrangé
2020-08-23 11:17 ` [PATCH v2 2/7] tests/docker: Install python3-setuptools in the debian9-mxe containers Thomas Huth
2020-09-01 16:19 ` Daniel P. Berrangé
2020-08-23 11:17 ` [PATCH v2 3/7] tests/Makefile: test-image-locking needs CONFIG_POSIX Thomas Huth
2020-09-01 16:21 ` Daniel P. Berrangé
2020-08-23 11:17 ` [PATCH v2 4/7] tests/Makefile: test-replication " Thomas Huth
2020-09-01 16:22 ` Daniel P. Berrangé
2020-08-23 11:17 ` [PATCH v2 5/7] dockerfiles/debian-win64-cross: Download WHPX MinGW headers Thomas Huth
2020-09-01 16:25 ` Daniel P. Berrangé
2020-09-01 16:31 ` Thomas Huth
2020-08-23 11:17 ` [PATCH v2 6/7] configure: Allow automatic WHPX detection Thomas Huth
2020-09-01 16:25 ` Daniel P. Berrangé
2020-08-23 11:17 ` [PATCH v2 7/7] gitlab-ci: Add cross-compiling build tests Thomas Huth
2020-09-01 16:27 ` Daniel P. Berrangé
2020-09-01 16:36 ` Thomas Huth [this message]
2020-08-25 7:59 ` [PATCH v2 0/7] Run cross-compilation build tests in the gitlab-CI Paolo Bonzini
2020-09-01 16:29 ` Daniel P. Berrangé
2020-09-01 16:38 ` 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=a39b632a-5d59-0a63-b342-644f052ee1ff@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=luoyonggang@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--cc=wainersm@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).