public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): sourceware-reconfig - failed '/sourceware/builder/bin/buildbot-reload.sh' (failure) (main)
Date: Thu, 30 Mar 2023 00:22:44 +0200	[thread overview]
Message-ID: <20230329222244.GH20220@gnu.wildebeest.org> (raw)
In-Reply-To: <20230329221916.5A8BF3858D3C@sourceware.org>

Hi,

On Wed, Mar 29, 2023 at 10:19:16PM +0000, builder@sourceware.org wrote:
> A new failure has been detected on builder sourceware-reconfig while building sourceware.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/60/builds/282
> 
> Build state: failed '/sourceware/builder/bin/buildbot-reload.sh' (failure)
> Revision: (unknown)
> Worker: sourceware
> Build Reason: (unknown)
> Blamelist: Mark Wielaard <mark@klomp.org>
> 
> Steps:
> 
> - 0: worker_preparation ( success )
> 
> - 1: git update ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/60/builds/282/steps/1/logs/stdio
> 
> - 2: checkconfig ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/60/builds/282/steps/2/logs/stdio
> 
> - 3: reload ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/60/builds/282/steps/3/logs/stdio
> 

Looks like it is just taking some time to reconfigure because it is really busy.
Lets give it some time then new valgrind-try builder isn't urgent.

Cheers,

Mark

  reply	other threads:[~2023-03-29 22:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 22:19 builder
2023-03-29 22:22 ` Mark Wielaard [this message]
2023-12-24 19:24 builder
2023-12-29  0:39 builder
2024-01-03  0:26 builder
2024-01-07 20:49 builder
2024-01-08 22:08 builder
2024-04-11 15:24 builder

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=20230329222244.GH20220@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=buildbot@sourceware.org \
    /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).