From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Willian Rampazzo" <willianr@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: Re: [PATCH 2/2] gitlab: skip many more targets in windows cross builds
Date: Wed, 11 Aug 2021 09:43:57 +0100 [thread overview]
Message-ID: <YRONzVe8Clct99j2@redhat.com> (raw)
In-Reply-To: <1a43f8c6-24f8-9aee-d321-04f5a8ecc6ee@amsat.org>
On Wed, Aug 11, 2021 at 08:20:37AM +0200, Philippe Mathieu-Daudé wrote:
> On 8/10/21 4:06 PM, Daniel P. Berrangé wrote:
> > The windows cross builds still take way too long in gitlab CI, so need
> > more targets to be skipped. We don't want to hurt coverage of other
> > cross builds more though, so we let jobs fine tune with a new env
> > variale $CROSS_SKIP_TARGETS.
> >
> > We take the set of targets that are considered relatively niche or
> > very old architectures, and skip approx half of them in win32 builds
> > and the other half of them in win64.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > .gitlab-ci.d/crossbuild-template.yml | 2 +-
> > .gitlab-ci.d/crossbuilds.yml | 2 ++
> > 2 files changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/.gitlab-ci.d/crossbuild-template.yml b/.gitlab-ci.d/crossbuild-template.yml
> > index cfb576b54c..10d22dcf6c 100644
> > --- a/.gitlab-ci.d/crossbuild-template.yml
> > +++ b/.gitlab-ci.d/crossbuild-template.yml
> > @@ -10,7 +10,7 @@
> > --disable-user --target-list-exclude="arm-softmmu cris-softmmu
> > i386-softmmu microblaze-softmmu mips-softmmu mipsel-softmmu
> > mips64-softmmu ppc-softmmu riscv32-softmmu sh4-softmmu
> > - sparc-softmmu xtensa-softmmu"
> > + sparc-softmmu xtensa-softmmu $CROSS_SKIP_TARGETS"
> > - make -j$(expr $(nproc) + 1) all check-build $MAKE_CHECK_ARGS
> > - if grep -q "EXESUF=.exe" config-host.mak;
> > then make installer;
> > diff --git a/.gitlab-ci.d/crossbuilds.yml b/.gitlab-ci.d/crossbuilds.yml
> > index 4ff3aa3cfc..a5f9dbcbeb 100644
> > --- a/.gitlab-ci.d/crossbuilds.yml
> > +++ b/.gitlab-ci.d/crossbuilds.yml
> > @@ -160,6 +160,7 @@ cross-win32-system:
> > job: win32-fedora-cross-container
> > variables:
> > IMAGE: fedora-win32-cross
> > + CROSS_SKIP_TARGETS: or1k-softmmu rx-softmmu sh4eb-softmmu sparc64-softmmu tricore-softmmu xtensaeb-softmmu
> > artifacts:
> > paths:
> > - build/qemu-setup*.exe
> > @@ -170,6 +171,7 @@ cross-win64-system:
> > job: win64-fedora-cross-container
> > variables:
> > IMAGE: fedora-win64-cross
> > + CROSS_SKIP_TARGETS: alpha-softmmu avr-softmmu hppa-softmmu m68k-softmmu microblazeel-softmmu mips64el-softmmu nios2-softmmu
>
> It looks you inverted the lists. We expect more Win64 users, and these
> are the targets of interest. I'd keep here (skipping in Win32):
I wouldn't say inverted, because the split was entirely arbitrary. While
32-bit vs 64-bit could conceivably show a difference, in practice those
differences are likely to already be caught by non-windows builds. These
jobs are most important for catching UNIX vs Windows differences, so in
that view whether a target is built for win32 vs win64 doesn't matter.
>
> alpha-softmmu avr-softmmu hppa-softmmu m68k-softmmu microblazeel-softmmu
> mips64el-softmmu sparc64-softmmu
>
> And skip (keep them in win32):
>
> or1k-softmmu rx-softmmu sh4eb-softmmu nios2-softmmu tricore-softmmu
> xtensaeb-softmmu
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-08-11 8:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 14:06 [PATCH 0/2] gitlab: avoid timeouts in windows cross builds Daniel P. Berrangé
2021-08-10 14:06 ` [PATCH 1/2] gitlab: exclude sparc-softmmu and riscv32-softmmu from " Daniel P. Berrangé
2021-08-10 14:56 ` Willian Rampazzo
2021-08-11 6:24 ` Philippe Mathieu-Daudé
2021-08-18 9:15 ` Mark Cave-Ayland
2021-08-18 9:29 ` Daniel P. Berrangé
2021-08-18 9:45 ` Mark Cave-Ayland
2021-08-18 10:23 ` Philippe Mathieu-Daudé
2021-08-10 14:06 ` [PATCH 2/2] gitlab: skip many more targets in windows " Daniel P. Berrangé
2021-08-10 14:59 ` Willian Rampazzo
2021-08-11 6:20 ` Philippe Mathieu-Daudé
2021-08-11 8:43 ` Daniel P. Berrangé [this message]
2021-08-11 5:53 ` [PATCH 0/2] gitlab: avoid timeouts " 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=YRONzVe8Clct99j2@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@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.