public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Dan Horák" <dhorak@redhat.com>
Cc: buildbot@sourceware.org
Subject: Re: Fedora upgrade on s390x lf-dev.marist and ppc64le fit.vutbr
Date: Fri, 17 Jun 2022 13:27:37 +0200	[thread overview]
Message-ID: <ac1eea5e2287e31376c8ce226fbc91f8f0a54eb1.camel@klomp.org> (raw)
In-Reply-To: <20220617123152.73a0bba289676793bad5846d@redhat.com>

Hi Dan,

On Fri, 2022-06-17 at 12:31 +0200, Dan Horák wrote:
> On Fri, 17 Jun 2022 11:19:46 +0200
> Mark Wielaard <mark@klomp.org> wrote:
> Fedora 34 just went EOL, so won't see any security updates
> > anymore. Could you upgrade the s390x and ppc64le workers at
> > lf-dev.marist and fit.vutbr to Fedora 35 or Fedora 36 for us?
> 
> yup, that's my plan for the next week or so. I will be upgrading the
> systems to F-36. Do you want a message about an exact time so you could
> disable the jobs or it doesn't matter?

Thanks! It shouldn't really matter when it is done exactly. Builds that
happen to be running are simply interrupted and should be retried when
the machine comes back up.

BTW. We are seeing high "steal times" on lfedora1. Some builds that
normally take a couple of minutes now take half an hour.
https://builder.sourceware.org/buildbot/#/builders/gdb-fedora-s390x

Cheers,

Mark

  reply	other threads:[~2022-06-17 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  9:19 Mark Wielaard
2022-06-17 10:31 ` Dan Horák
2022-06-17 11:27   ` Mark Wielaard [this message]
2022-06-17 11:53     ` Dan Horák
2022-06-20 12:59     ` Dan Horák
2022-06-20 12:55 ` Dan Horák

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=ac1eea5e2287e31376c8ce226fbc91f8f0a54eb1.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=buildbot@sourceware.org \
    --cc=dhorak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).