From: Mark Wielaard <mark@klomp.org>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
Binutils Mailing List <binutils@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>, buildbot@sourceware.org
Subject: Re: Buildbot failures due to checkout
Date: Thu, 25 Aug 2022 14:18:11 +0200 [thread overview]
Message-ID: <58db67f040fc9c13e63f723777e98f594f421784.camel@klomp.org> (raw)
In-Reply-To: <61518857-6ce4-ef34-9592-5d529cc0c21d@foss.arm.com>
Hi Richard,
On Thu, 2022-08-25 at 11:13 +0100, Richard Earnshaw via Binutils wrote:
> It seems that the buildbot is failing regularly due to git checkouts not
> succeeding. I'm guessing this is because it's using anonymous git
> access and therefore being throttled due to server load. But it's
> leading to a lot of additional 'spam' on the mailing list.
>
> Is there anything that can be done about this? Either by nobbling the
> bot to not whinge in this case or by giving the bot more priority on the
> server so that it doesn't get throttled so often.
Yeah, my apologies. It is a TODO item:
https://sourceware.org/git/?p=builder.git;a=blob;f=TODO;hb=HEAD
- Git retry step is broken. Looking at the code it only works for
incremental updates, not for mode='full', method='fresh' which we
are using. Given we often already use srcdir != builddir we might
just use incremental mode. Or we could fix the code?
I see there was just the following commit upstream:
git: Do not throw on intial _fetch() failure if retry or clobber
requested
https://github.com/buildbot/buildbot/commit/b2cad8d2840a74455366ddc1db0bcf4fd199125c
Maybe that would fix it. I'll see if I can backport that to our release
or hope there will be a new upstream release soon to upgrade to.
Frank, could we add the worker IPs to some allow list on sourceware?
There are 25+ workers now though (hurrah for success!)
https://builder.sourceware.org/buildbot/#/workers
Cheers,
Mark
parent reply other threads:[~2022-08-25 12:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <61518857-6ce4-ef34-9592-5d529cc0c21d@foss.arm.com>]
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=58db67f040fc9c13e63f723777e98f594f421784.camel@klomp.org \
--to=mark@klomp.org \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=binutils@sourceware.org \
--cc=buildbot@sourceware.org \
--cc=fche@elastic.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).