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 5FB7B3858428 for ; Mon, 7 Mar 2022 14:23:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5FB7B3858428 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 50489301FEB8; Mon, 7 Mar 2022 15:23:44 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 83C98401ED8D; Mon, 7 Mar 2022 15:23:43 +0100 (CET) Message-ID: <78c86cf8e9fd5a8c6c4dd9a000432d7e65f1014f.camel@klomp.org> Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset From: Mark Wielaard To: Arthur Cohen , buildbot@builder.wildebeest.org, gcc-rust@gcc.gnu.org Date: Mon, 07 Mar 2022 15:23:43 +0100 In-Reply-To: <9c0cd043-74a3-5db7-0265-5a6405f14f0e@embecosm.com> References: <20220307094957.0FEB68021E3@builder.wildebeest.org> <9c0cd043-74a3-5db7-0265-5a6405f14f0e@embecosm.com> 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=-3.8 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.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: Mon, 07 Mar 2022 14:23:48 -0000 Hi, On Mon, 2022-03-07 at 10:57 +0100, Arthur Cohen wrote: > This is due to the lexer's fix not being in yet. I think it should > be=20 > resolved later as soon as bors merges the fix, but I'll check just in > case. According to: https://builder.wildebeest.org/buildbot/#/builders?tags=3Dgccrust It was fixed by: commit 7a3c935c0f220835c001307944587a84c5af0192 Author: Philip Herron Date: Fri Mar 4 13:45:34 2022 +0000 Check if this constant item might already be compiled Which is slightly odd, because that isn't a lexer fix. So I suspect the bug is still there, but is hidden again. Cheers, Mark