All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Daniel Henrique Barboza" <danielhb413@gmail.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>
Subject: Re: Getting rid of the last bits of QEMU's 'ad-hoc CI' for merges
Date: Mon, 16 May 2022 16:58:04 +0100	[thread overview]
Message-ID: <YoJ0jEH9eNbeTtz9@redhat.com> (raw)
In-Reply-To: <3c93e737-538a-aacc-e893-3f9e2c0f4692@kaod.org>

On Mon, May 16, 2022 at 04:50:29PM +0200, Cédric Le Goater wrote:
> On 5/16/22 15:55, Peter Maydell wrote:
> > On Mon, 16 May 2022 at 14:51, Cédric Le Goater <clg@kaod.org> wrote:
> > > 
> > > On 5/16/22 14:43, Peter Maydell wrote:
> > > > I think we can get away with just dropping ppc64be -- we have
> > > > coverage for it as a cross-compile setup, and hopefully the
> > > > s390x CI runner will catch the various "fails tests on big-endian host"
> > > > issues. (Alternatively if anybody has a ppc64be machine they'd like
> > > > to let us run a gitlab CI runner on, we could do that :-))
> > > 
> > > No recent HW (P8 and above) would run a PPC64 BE distro if LE is
> > > supported by HW.
> > 
> > FWIW, the machine I use for ad-hoc CI is one in the gcc compile
> > farm, which is supposedly a "IBM POWER8 8284-22A", running Debian sid.
> 
> Since the P8 have been around (~2014), the focus is really on LE.
> I think debian is the last distro still providing BE binaries.
> But no iso, you have to start with a debian 1O and do the upgrade.

If even Debian 11 has stopped providing ppc64be images, then
the end really is nigh. We still support Debian 10 as a target
in our platform support matrix until Debin 12 comes out in
mid/late 2023.

So IMHO we've got at most 1 year left of needing to worry
about ppc64be targets.

> > If BE PPC is fading away then that's another argument for
> > living with the loss of CI coverage, I guess.
> 
> yes.
> 
> It would good to keep a BE host for test coverage. It doesn't have
> to be ppc64be if it is too complex to maintain.

IIUC, we've got s390x giving BE coverage right now, at least
for certain configure option combinations.
 
> I can help on setting up a debian BE sid vm on the above IBM POWER8
> 8284-22A system if you need to. I have an image ready to use.

If we have a means to run CI for the next ~1 year great, but it
doesn't seem like worth investing masses of resources into it.

With 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 :|



  reply	other threads:[~2022-05-16 16:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 12:43 Getting rid of the last bits of QEMU's 'ad-hoc CI' for merges Peter Maydell
2022-05-16 13:51 ` Cédric Le Goater
2022-05-16 13:55   ` Peter Maydell
2022-05-16 14:50     ` Cédric Le Goater
2022-05-16 15:58       ` Daniel P. Berrangé [this message]
2022-05-16 14:26 ` Paolo Bonzini
2022-05-16 14:30 ` Thomas Huth
2022-05-16 14:35   ` Peter Maydell
2022-05-16 15:25     ` Stefan Hajnoczi

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=YoJ0jEH9eNbeTtz9@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    --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 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.