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 E9D703858C83 for ; Wed, 17 Aug 2022 12:47:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E9D703858C83 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 reform (unknown [178.228.156.55]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id A7443300070C; Wed, 17 Aug 2022 14:47:18 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 6258B2E81D4C; Wed, 17 Aug 2022 13:30:36 +0200 (CEST) Date: Wed, 17 Aug 2022 13:30:36 +0200 From: Mark Wielaard To: Jan Beulich Cc: buildbot@sourceware.org Subject: Re: =?utf-8?Q?=E2=98=A0_Buildbot_=28GN?= =?utf-8?Q?U?= Toolchain): binutils-gdb - failed update (failure) (master) Message-ID: References: <20220816074708.104EA3858418@sourceware.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.2 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 X-BeenThere: buildbot@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "The https://builder.sourceware.org/ buildbot" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2022 12:47:22 -0000 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 > > 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