From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: "Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Willian Rampazzo" <willianr@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 1/2] gitlab: exclude sparc-softmmu and riscv32-softmmu from cross builds
Date: Wed, 18 Aug 2021 10:29:00 +0100 [thread overview]
Message-ID: <YRzS3F766na8QeJm@redhat.com> (raw)
In-Reply-To: <11174538-e2fb-cd99-de92-3153fa56d017@ilande.co.uk>
On Wed, Aug 18, 2021 at 10:15:47AM +0100, Mark Cave-Ayland wrote:
> On 10/08/2021 15:06, Daniel P. Berrangé wrote:
>
> > We need to cut down compile time by excluding more targets. Both these
> > targets still have their 64-bit variant enabled, so the loss of coverage
> > is mitigated to some degree.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > .gitlab-ci.d/crossbuild-template.yml | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/.gitlab-ci.d/crossbuild-template.yml b/.gitlab-ci.d/crossbuild-template.yml
> > index 7d3ad00a1e..cfb576b54c 100644
> > --- a/.gitlab-ci.d/crossbuild-template.yml
> > +++ b/.gitlab-ci.d/crossbuild-template.yml
> > @@ -9,7 +9,8 @@
> > ../configure --enable-werror --disable-docs $QEMU_CONFIGURE_OPTS
> > --disable-user --target-list-exclude="arm-softmmu cris-softmmu
> > i386-softmmu microblaze-softmmu mips-softmmu mipsel-softmmu
> > - mips64-softmmu ppc-softmmu sh4-softmmu xtensa-softmmu"
> > + mips64-softmmu ppc-softmmu riscv32-softmmu sh4-softmmu
> > + sparc-softmmu xtensa-softmmu"
> > - make -j$(expr $(nproc) + 1) all check-build $MAKE_CHECK_ARGS
> > - if grep -q "EXESUF=.exe" config-host.mak;
> > then make installer;
>
> I'd prefer to keep sparc-softmmu if possible, simply because my everyday
> platform is Linux and so having a cross-build for Windows will catch things
> that I may miss on a day-to-day basis. Is sparc-softmmu currently enabled as
> part of the native MINGW64 build?
Note the builds still include 'sparc64-softmmu', so we're only loosing
cover in places where it diverges fromthe 64-bit build, but this will
sstil get coverage in native builds.
> If I go to my Gitlab QEMU fork Settings -> CI/CD -> Variables there is an
> option to set variables that can be used in job scripts. Perhaps this could
> be used so that I can configure my personal QEMU fork to always run
> sparc-softmmu builds when preparing PRs even if they aren't enabled for
> everyone by default? At least this would then allow me to spot any breakage
> before sending a final PR to Peter.
Separately from this I'm doing some work to make things more configurable
https://lists.gnu.org/archive/html/qemu-devel/2021-08/msg02102.html
but not on this level of granularity.
Rather than globally excluding from all cross builds, I think we ought to
split it up more equitably acrss the different builds in some way.
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-18 9:30 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é [this message]
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é
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=YRzS3F766na8QeJm@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=mark.cave-ayland@ilande.co.uk \
--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.