From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 3C3523858D28; Thu, 25 Aug 2022 12:18:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3C3523858D28 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 22CB0302AB2C; Thu, 25 Aug 2022 14:18:12 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 2146B403B351; Thu, 25 Aug 2022 14:18:12 +0200 (CEST) Message-ID: <58db67f040fc9c13e63f723777e98f594f421784.camel@klomp.org> Subject: Re: Buildbot failures due to checkout From: Mark Wielaard To: Richard Earnshaw , Binutils Mailing List Cc: "Frank Ch. Eigler" , buildbot@sourceware.org Date: Thu, 25 Aug 2022 14:18:11 +0200 In-Reply-To: <61518857-6ce4-ef34-9592-5d529cc0c21d@foss.arm.com> References: <61518857-6ce4-ef34-9592-5d529cc0c21d@foss.arm.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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= =20 > succeeding. I'm guessing this is because it's using anonymous git=20 > access and therefore being throttled due to server load. But it's=20 > leading to a lot of additional 'spam' on the mailing list. >=20 > Is there anything that can be done about this? Either by nobbling the= =20 > bot to not whinge in this case or by giving the bot more priority on the= =20 > server so that it doesn't get throttled so often. Yeah, my apologies. It is a TODO item: https://sourceware.org/git/?p=3Dbuilder.git;a=3Dblob;f=3DTODO;hb=3DHEAD - Git retry step is broken. Looking at the code it only works for incremental updates, not for mode=3D'full', method=3D'fresh' which we are using. Given we often already use srcdir !=3D 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/b2cad8d2840a74455366ddc1db0bcf4= fd199125c 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