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 3B5253948825 for ; Wed, 23 Feb 2022 11:26:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3B5253948825 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 99FF030008A9; Wed, 23 Feb 2022 12:26:27 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id F1309409485C; Wed, 23 Feb 2022 12:26:26 +0100 (CET) Message-ID: Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset From: Mark Wielaard To: buildbot@builder.wildebeest.org Cc: gcc-rust@gcc.gnu.org Date: Wed, 23 Feb 2022 12:26:26 +0100 In-Reply-To: References: <20220223102616.E186F802A30@builder.wildebeest.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.1 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: Wed, 23 Feb 2022 11:26:30 -0000 Hi, On Wed, 2022-02-23 at 11:35 +0100, Mark Wielaard wrote: > So, this works as expected. Note that it reports issues not just for > debian-i386, but also for some other arches (all debian based). The > i386 issues are not new. But the others do seem to be caused by the > latest commit. I haven't investigated why yet though. >=20 > The buildbot links also point to the log and sum files that might be > useful to inspect. So there were 3 issues: - The debian-i386 build had pre-existing failures that weren't reported before. - The recent commits introduced some tests which failed, and then some code changes that fixed those tests so they succeeded. IMHO the buildbot was correct to flag those because they are real failures, even though they were fixed 2 commits later. This makes e.g. bisecting issues a bit of a pain. So I would like to see us commit in the "correct order". - The buildbot test was incorrect when /bin/sh wasn't bash (as on the debian builders, where it is dash). test $? =3D=3D 1 should have been $? -eq 1 Fixed. Cheers, Mark