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 A1DE83848E25; Tue, 6 Dec 2022 15:36:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A1DE83848E25 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 A0886300071F; Tue, 6 Dec 2022 16:36:49 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id B8923403B324; Tue, 6 Dec 2022 16:36:48 +0100 (CET) Message-ID: <800d86b48f0833485cd46ca8771cab37d2458e8e.camel@klomp.org> Subject: Re: =?UTF-8?Q?=E2=98=A0?= Buildbot (GNU Toolchain): sourceware-reconfig - failed '/sourceware/builder/bin/buildbot-reload.sh' (failure) (main) From: Mark Wielaard To: builder@sourceware.org, buildbot@sourceware.org Date: Tue, 06 Dec 2022 16:36:48 +0100 In-Reply-To: <20221206144940.95AE5382E450@sourceware.org> References: <20221206144940.95AE5382E450@sourceware.org> 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=-3032.8 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP 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, On Tue, 2022-12-06 at 14:49 +0000, builder@sourceware.org wrote: > A new failure has been detected on builder sourceware-reconfig while > building sourceware. >=20 > Full details are available at: > https://builder.sourceware.org/buildbot/#builders/60/builds/234 >=20 > Build state: failed '/sourceware/builder/bin/buildbot-reload.sh' > (failure) Apparently the builder was really busy and it took too long so the reconfig step. It did eventually happen though: 2022-12-06 15:27:50+0000 [-] configuration update complete (took 2313.681 seconds) And everything is still running fine. Cheers, Mark