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 02E6C3959C85 for ; Tue, 10 May 2022 11:38:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 02E6C3959C85 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 725FC3000599 for ; Tue, 10 May 2022 13:38:16 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id C442B4058739; Tue, 10 May 2022 13:38:14 +0200 (CEST) Message-ID: <179888aa6094ad8c00dc3bb07f53695f0c5ccceb.camel@klomp.org> Subject: Re: =?UTF-8?Q?=E2=98=A0?= Buildbot (GNU Toolchain): gccrust - failed 'grep unexpected ...' (failure) (master) From: Mark Wielaard To: gcc-rust@gcc.gnu.org Date: Tue, 10 May 2022 13:38:14 +0200 In-Reply-To: <20220510110040.F2F743955628@sourceware.org> References: <20220510110040.F2F743955628@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=-4.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-rust@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: gcc-rust mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2022 11:38:19 -0000 On Tue, 2022-05-10 at 11:00 +0000, builder--- via Gcc-rust wrote: > A new failure has been detected on builder gccrust-debian-i386 while > building gccrust. >=20 > Full details are available at: > https://builder.sourceware.org/buildbot/#builders/27/builds/98 Just when we were all green :{ It isn't clear to me what bors is doing though. It seems to just throw in commits randomly and then tries to fix things up with a merge commit. Is there any way to make bors not do that? It makes the buildbot unhappy and makes bisecting commits really hard. Ideally all commits are done on top of the tree without these odd merge commits. So do a simple rebase first, then commit/push. Cheers, Mark