From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>, "Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH] shippable.yml: Remove jobs duplicated on Gitlab-CI
Date: Fri, 8 Jan 2021 15:21:21 +0000 [thread overview]
Message-ID: <20210108152121.GK1082385@redhat.com> (raw)
In-Reply-To: <28635389-fbe2-89eb-5ec6-5fdc1da98c6a@redhat.com>
On Fri, Jan 08, 2021 at 04:14:30PM +0100, Paolo Bonzini wrote:
> On 08/01/21 15:51, Philippe Mathieu-Daudé wrote:
> > The following jobs are duplicated on Gitlab-CI since commit
> > 6bcb5fc0f7a ("gitlab-ci: Add cross-compiling build tests"):
> >
> > - IMAGE=debian-armel-cross
> >
> > TARGET_LIST=arm-softmmu -> cross-armel-system
> > TARGET_LIST=arm-linux-user -> cross-armel-user
> > TARGET_LIST=armeb-linux-user -> cross-armel-user
> >
> > - IMAGE=debian-armhf-cross
> >
> > TARGET_LIST=arm-softmmu -> cross-armhf-system
> > TARGET_LIST=arm-linux-user -> cross-armhf-user
> > TARGET_LIST=armeb-linux-user -> cross-armhf-user
> >
> > - IMAGE=debian-arm64-cross
> >
> > TARGET_LIST=aarch64-softmmu -> cross-arm64-system
> > TARGET_LIST=aarch64-linux-user -> cross-arm64-user
> >
> > - IMAGE=debian-s390x-cross
> >
> > TARGET_LIST=s390x-softmmu -> cross-s390x-system
> > TARGET_LIST=s390x-linux-user -> cross-s390x-user
> >
> > - IMAGE=debian-mips-cross
> >
> > TARGET_LIST=mipsel-linux-user -> cross-mips-user
> >
> > - IMAGE=debian-mips64el-cross
> >
> > TARGET_LIST=mips64el-softmmu -> cross-mips64el-system
> > TARGET_LIST=mips64el-linux-user -> cross-mips64el-user
> >
> > - IMAGE=debian-ppc64el-cross
> >
> > TARGET_LIST=ppc64-softmmu -> cross-ppc64el-system
> > TARGET_LIST=ppc64-linux-user -> cross-ppc64el-user
> > TARGET_LIST=ppc64abi32-linux-user -> cross-ppc64el-user
> >
> > Remove them from Shippable CI.
> >
> > Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> > ---
> > .shippable.yml | 14 +-------------
> > 1 file changed, 1 insertion(+), 13 deletions(-)
> >
> > diff --git a/.shippable.yml b/.shippable.yml
> > index 14350e6de8a..97bfa2a0f38 100644
> > --- a/.shippable.yml
> > +++ b/.shippable.yml
> > @@ -7,20 +7,8 @@ env:
> > matrix:
> > - IMAGE=debian-amd64
> > TARGET_LIST=x86_64-softmmu,x86_64-linux-user
> > - - IMAGE=debian-armel-cross
> > - TARGET_LIST=arm-softmmu,arm-linux-user,armeb-linux-user
> > - - IMAGE=debian-armhf-cross
> > - TARGET_LIST=arm-softmmu,arm-linux-user,armeb-linux-user
> > - - IMAGE=debian-arm64-cross
> > - TARGET_LIST=aarch64-softmmu,aarch64-linux-user
> > - - IMAGE=debian-s390x-cross
> > - TARGET_LIST=s390x-softmmu,s390x-linux-user
> > - IMAGE=debian-mips-cross
> > - TARGET_LIST=mips-softmmu,mipsel-linux-user
> > - - IMAGE=debian-mips64el-cross
> > - TARGET_LIST=mips64el-softmmu,mips64el-linux-user
> > - - IMAGE=debian-ppc64el-cross
> > - TARGET_LIST=ppc64-softmmu,ppc64-linux-user,ppc64abi32-linux-user
> > + TARGET_LIST=mips-softmmu
>
> The debian-mips-cross/mips-softmmu pair (and also mipsel-softmmu) is
> currently excluded by Gitlab's cross-mips-system, is there a reason for
> that? If we add it there, we can just remove shippable altogether.
Some softmmu targets were disable to keep the build time under control.
We could enable a different subset of targets for each cross host arch,
so that overall we get representative coverage of the full set.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-01-08 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 14:51 [PATCH] shippable.yml: Remove jobs duplicated on Gitlab-CI Philippe Mathieu-Daudé
2021-01-08 15:14 ` Paolo Bonzini
2021-01-08 15:21 ` Daniel P. Berrangé [this message]
2021-01-08 15:36 ` Paolo Bonzini
2021-01-10 11:00 ` Philippe Mathieu-Daudé
2021-01-08 16:42 ` Alex Bennée
2021-01-12 9:34 ` 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=20210108152121.GK1082385@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--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 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).