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 3F1A43858415
 for <gcc-rust@gcc.gnu.org>; Sat,  5 Feb 2022 17:12:47 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3F1A43858415
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 B0605303C3EC;
 Sat,  5 Feb 2022 18:12:45 +0100 (CET)
Received: by tarox.wildebeest.org (Postfix, from userid 1000)
 id 5BF7D40010D8; Sat,  5 Feb 2022 18:12:45 +0100 (CET)
Message-ID: <5d3f75358ffa7602b0bbf53235a83c8d71bbf067.camel@klomp.org>
Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset
From: Mark Wielaard <mark@klomp.org>
To: buildbot@builder.wildebeest.org, gcc-rust@gcc.gnu.org
Date: Sat, 05 Feb 2022 18:12:45 +0100
In-Reply-To: <20220205165808.ED561801D13@builder.wildebeest.org>
References: <20220205165808.ED561801D13@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 <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: Sat, 05 Feb 2022 17:12:49 -0000

Hi,

On Sat, 2022-02-05 at 16:58 +0000, buildbot@builder.wildebeest.org
wrote:
> The Buildbot has detected a new failure on builder gccrust-debian-arm64 w=
hile building gccrust.
> Full details are available at:
>     https://builder.wildebeest.org/buildbot/#builders/58/builds/1620
>=20
> Buildbot URL: https://builder.wildebeest.org/buildbot/
>=20
> Worker for this Build: debian-arm64
>=20
> Build Reason: <unknown>
> Blamelist: CohenArthur <arthur.cohen@epita.fr>, bors[bot] <26634292+bors[=
bot]@users.noreply.github.com>
>=20
> BUILD FAILED: failed compile (failure)

This was caused by two commits being flipped:

commit bc47ace0ec97ef1b3498c17ff03e2ee873743d5c
Author: CohenArthur <cohenarthur.dev@gmail.com>
Date:   Tue Jan 25 13:59:06 2022 +0100

    selftest: Move C specific tests in c_family_test()

commit 2b1345a73654cf5b2b13e334813ee97016ba5d1a
Author: CohenArthur <arthur.cohen@epita.fr>
Date:   Tue Oct 19 10:46:45 2021 +0200

    selftest: Enable unit testing for the rust frontend

So the first commit enabled the selftests (which fails in the buildbot)
and the second moved the C specific selftests (which just failed) into
c_family_tests so they won't trigger a failure next time.

Unfortunately the buildbot thinks the second commit isn't rust frontend
related (which is technically correct) and so won't do a build with
that commit.

But the next gccrs commit should turn the buildbot green again.

Cheers,

Mark