All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Michael Tokarev" <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
	"Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v2] Re-enable riscv64-debian-cross-container (debian riscv64 is finally usable again!)
Date: Fri, 3 May 2024 11:12:14 +0100	[thread overview]
Message-ID: <ZjS4fqE1OdpTgeMq@redhat.com> (raw)
In-Reply-To: <ZjSbRsOpJsTdTh6l@redhat.com>

On Fri, May 03, 2024 at 09:07:34AM +0100, Daniel P. Berrangé wrote:
> On Fri, May 03, 2024 at 10:16:34AM +0300, Michael Tokarev wrote:
> > Revert "gitlab-ci: Disable the riscv64-debian-cross-container by default"
> > This reverts commit f51f90c65ed7706c3c4f7a889ce3d6b7ab75ef6a.
> > 
> > riscv64 in debian has been non-functioning for almost a year, after the
> > architecture has been promoted to release architecture and all binary
> > packages started to be re-built, making the port not multi-arch-co-installable
> > for a long time (in debian, multi-arch packages must be of the same version,
> > but when a package is rebuilt on one architecture it gets a version bump too).
> > Later on, debiah had a long time64_t transition which made sid unusable for
> > quite some time too.  Both such events happens in debian very rarely (like,
> > once in 10 years or so - for example, previous big transition like that was
> > libc5 => libc6 transition).  Now both of these are finished (where qemu is
> > concerned anyway).
> > 
> > Hopefully debian unstable wont be very unstable.  At the very least it is
> > better to have sporadic CI failures here than no riscv64 coverage at all.
> 
> IME of running Debian sid in CI pipelines for libvirt, it is
> way too unstable to be used as a gating job. There are periods
> weeks-long when packages fail to install, even for relatively
> mainstream arch targets like x86, let alone a new target like
> riscv.

BTW, I don't mean this to be a criticism of Debian. We've seen
the same kind of instability with all the other non-released distros
(Fedora Rawhide, OpenSUSE Tumbleweed and Alpine Edge) in libvirt CI,
such that we've finally set all of them non-gating across all our CI
deployments.

They're all good to have in CI as a smoke test to identify possible
problems coming towards you in the next stable release, but false
failures have to be expected.

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



  parent reply	other threads:[~2024-05-03 10:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03  7:16 [PATCH v2] Re-enable riscv64-debian-cross-container (debian riscv64 is finally usable again!) Michael Tokarev
2024-05-03  7:34 ` Thomas Huth
2024-05-03  8:07 ` Daniel P. Berrangé
2024-05-03  8:51   ` Philippe Mathieu-Daudé
2024-05-03  9:21     ` Daniel P. Berrangé
2024-05-03 10:07   ` Alex Bennée
2024-05-03 10:12   ` Daniel P. Berrangé [this message]
2024-05-13  4:06 ` Alistair Francis

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=ZjS4fqE1OdpTgeMq@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=mjt@tls.msk.ru \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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 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.