All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
	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] Re-enable riscv64-debian-cross-container (debian riscv64 is finally usable again!)
Date: Fri, 3 May 2024 09:05:09 +0100	[thread overview]
Message-ID: <ZjSatbLY1U8QQRaw@redhat.com> (raw)
In-Reply-To: <34584520-cf5d-47c8-a8a2-ca177a89edef@tls.msk.ru>

On Thu, May 02, 2024 at 11:54:15PM +0300, Michael Tokarev wrote:
> 02.05.2024 23:41, Richard Henderson wrote:
> > On 5/2/24 13:08, Michael Tokarev wrote:
> > > This thing works now with sid/unstable, this is what this patch is about.
> > 
> > It worked when first introduced, then failed, then worked...
> > Sid is too unstable for our usage as a gating test.
> 
> unstable can be unstable at times.  Generally it works, and can fail
> during short periods.
> 
> riscv64 didn't work since it got promoted to release arch last year, due
> to non-working multiarch because many riscv64 packages in debian had
> different version numbers compared to other architectures (due to rebuilds
> of binaries).  Later on whole sid was broken by a large time64 transition
> and a lot of breakages in this area.  This is now being completed and
> is migrated to testing, which is finally available for riscv64 too as
> a release arch.
> 
> I wouldn't switch to testing just yet, because at this point, unstable
> will usually be more stable, or, rather, it will be broken for much
> shorter periods of time than testing, due to migration delays.
> 
> It will take some more time for debian testing to become more or less
> stable in this context.  But lack of riscv testing already cost me a
> *stable* release which failed to *build* (8.2.3 fails to build on
> riscv64).  So I think it is more important to run this job on sid
> than not to run it at all.

JOB_OPTIONAL requires a job to be manually started, but is
non-gating.

We need something intermediate, that always starts the job,
but still keeps it non-gating. You'll see if the pipeline
job for riscv is green or yellow (failure), and can then
check if its a real failure of a Debian failure.


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:[~2024-05-03  8:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 19:40 [PATCH] Re-enable riscv64-debian-cross-container (debian riscv64 is finally usable again!) Michael Tokarev
2024-05-02 19:59 ` Michael Tokarev
2024-05-02 20:05 ` Richard Henderson
2024-05-02 20:08   ` Michael Tokarev
2024-05-02 20:41     ` Richard Henderson
2024-05-02 20:54       ` Michael Tokarev
2024-05-03  8:05         ` Daniel P. Berrangé [this message]
2024-05-03  5:06     ` 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=ZjSatbLY1U8QQRaw@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=richard.henderson@linaro.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.