From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mark@klomp.org>
Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184])
 by sourceware.org (Postfix) with ESMTPS id A7BB1385841D
 for <gcc-rust@gcc.gnu.org>; Wed,  2 Mar 2022 10:00:36 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A7BB1385841D
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 C6416300027E;
 Wed,  2 Mar 2022 11:00:34 +0100 (CET)
Received: by tarox.wildebeest.org (Postfix, from userid 1000)
 id 26DEF413CD0E; Wed,  2 Mar 2022 11:00:34 +0100 (CET)
Message-ID: <4ca07ce009796b14cfe3f4ddef9212e280d2d52b.camel@klomp.org>
Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset
From: Mark Wielaard <mark@klomp.org>
To: Philip Herron <philip.herron@embecosm.com>, Thomas Schwinge
 <thomas@codesourcery.com>
Cc: buildbot@builder.wildebeest.org, Arthur Cohen
 <arthur.cohen@embecosm.com>,  gcc-rust@gcc.gnu.org
Date: Wed, 02 Mar 2022 11:00:34 +0100
In-Reply-To: <CAB2u+n2QZRsroKZ1sN66wjKMy9sr2qkZ+PnD1xMrLpoFfZWntg@mail.gmail.com>
References: <20220301190815.EE6CD8176B0@builder.wildebeest.org>
 <Yh6pHSrMO6MZR8zW@wildebeest.org>
 <87ee3kstu1.fsf@euler.schwinge.homeip.net>
 <CAB2u+n2QZRsroKZ1sN66wjKMy9sr2qkZ+PnD1xMrLpoFfZWntg@mail.gmail.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 <gcc-rust.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-rust>,
 <mailto:gcc-rust-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-rust/>
List-Post: <mailto:gcc-rust@gcc.gnu.org>
List-Help: <mailto:gcc-rust-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-rust>,
 <mailto:gcc-rust-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2022 10:00:40 -0000

Hi,

On Wed, 2022-03-02 at 09:03 +0000, Philip Herron wrote:
> Yet again the build bots are out doing github automation :D. Would
> you
> be able to give Arthur access to the failing buildbot to test his
> fix?

Sure. Arthur can you sent me your ssh pubkey?

> We think we know what the issue is. We changed the lexer so we could
> give it a buffer instead of a file for macro expansion, but the
> string
> is going out of scope when we set it up.

Aha. That explains why the lexer is seeing garbage. At least in my
local case. I am slightly surprised it isn't showing up locally for
you. What triggers the running of the selftests?

Cheers,

Mark