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 9A5E6385AC3D for ; Wed, 23 Feb 2022 10:35:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 9A5E6385AC3D 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 (deer0x16.wildebeest.org [172.31.17.152]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 7FD2B30008A9; Wed, 23 Feb 2022 11:35:40 +0100 (CET) Received: by reform (Postfix, from userid 1000) id E5B502E813D1; Wed, 23 Feb 2022 11:35:39 +0100 (CET) Date: Wed, 23 Feb 2022 11:35:39 +0100 From: Mark Wielaard To: buildbot@builder.wildebeest.org Cc: gcc-rust@gcc.gnu.org Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset Message-ID: References: <20220223102616.E186F802A30@builder.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220223102616.E186F802A30@builder.wildebeest.org> X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_SHORT, 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 10:35:44 -0000 Hi, 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. The buildbot links also point to the log and sum files that might be useful to inspect. Cheers, Mark On Wed, Feb 23, 2022 at 10:26:16AM +0000, buildbot@builder.wildebeest.org wrote: > The Buildbot has detected a new failure on builder gccrust-debian-arm64 while building gccrust. > Full details are available at: > https://builder.wildebeest.org/buildbot/#builders/58/builds/1681 > > Buildbot URL: https://builder.wildebeest.org/buildbot/ > > Worker for this Build: debian-arm64 > > Build Reason: > Blamelist: Arthur Cohen , bors[bot] <26634292+bors[bot]@users.noreply.github.com> > > BUILD FAILED: failed 'grep unexpected ...' (failure) > > Sincerely, > -The BuildbotThe Buildbot has detected a new failure on builder gccrust-debian-i386 while building gccrust. > Full details are available at: > https://builder.wildebeest.org/buildbot/#builders/62/builds/1316 > > Buildbot URL: https://builder.wildebeest.org/buildbot/ > > Worker for this Build: debian-i386 > > Build Reason: > Blamelist: Arthur Cohen , bors[bot] <26634292+bors[bot]@users.noreply.github.com> > > BUILD FAILED: failed 'grep unexpected ...' (failure) > > Sincerely, > -The BuildbotThe Buildbot has detected a new failure on builder gccrust-debian-ppc64 while building gccrust. > Full details are available at: > https://builder.wildebeest.org/buildbot/#builders/64/builds/139 > > Buildbot URL: https://builder.wildebeest.org/buildbot/ > > Worker for this Build: debian-ppc64 > > Build Reason: > Blamelist: Arthur Cohen , bors[bot] <26634292+bors[bot]@users.noreply.github.com> > > BUILD FAILED: failed 'grep unexpected ...' (failure) > > Sincerely, > -The Buildbot > > -- > Gcc-rust mailing list > Gcc-rust@gcc.gnu.org > https://gcc.gnu.org/mailman/listinfo/gcc-rust