From: Mark Wielaard <mark@klomp.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: buildbot@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed update (failure) (master)
Date: Wed, 17 Aug 2022 13:30:36 +0200 [thread overview]
Message-ID: <YvzRXNx8Tcxrtv4/@wildebeest.org> (raw)
In-Reply-To: <de9b1e96-3e5f-fbc5-dd64-6254ffc80273@suse.com>
Hi Jan,
On Tue, Aug 16, 2022 at 09:52:39AM +0200, Jan Beulich wrote:
> On 16.08.2022 09:47, builder@sourceware.org wrote:
> > A new failure has been detected on builder binutils-debian-testing-x86_64 while building binutils-gdb.
> >
> > Full details are available at:
> > https://builder.sourceware.org/buildbot/#builders/149/builds/233
> >
> > Build state: failed update (failure)
> > Revision: (unknown)
> > Worker: bbo1-1
> > Build Reason: (unknown)
> > Blamelist: Jan Beulich <jbeulich@suse.com>
>
> I consider this wrong for ...
>
> > Steps:
> >
> > - 0: worker_preparation ( success )
> >
> > - 1: git checkout ( failure )
> > Logs:
> > - stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/233/steps/1/logs/stdio
>
> ... this kind of failure, which has been happening repeatedly. Correcting this
> would then likely also lead to such mails no longer being sent to individuals,
> but - if at all - to the list only.
Agreed. It doesn't actually happen that often, maybe once in the 200
builds, but we are doing 500 builds a day. So it definitely happens
multiple times a day now :{
It looks like a bug in buildbot, normally transient network issues
should just be retried. But for some reason the get fetch step as we
use it generates a hard error. See also the TODO file. It might be
that a fix is already upstream and we'll get it when upgrading when a
new version is released. If that doesn't happen soon I'll try
backporting that fix and/or do the git fetch updates differently.
Cheers,
Mark
next parent reply other threads:[~2022-08-17 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220816074708.104EA3858418@sourceware.org>
[not found] ` <de9b1e96-3e5f-fbc5-dd64-6254ffc80273@suse.com>
2022-08-17 11:30 ` Mark Wielaard [this message]
[not found] <20220721194111.2AE56383A37A@sourceware.org>
[not found] ` <56af4b2b-e87c-6fd0-e5c1-93f834947bdd@arm.com>
2022-07-22 9:58 ` Mark Wielaard
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=YvzRXNx8Tcxrtv4/@wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=jbeulich@suse.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).