From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mark@klomp.org>
Received: from gnu.wildebeest.org (wildebeest.demon.nl [212.238.236.112])
 by sourceware.org (Postfix) with ESMTPS id 66C9F39ADC1B
 for <gcc-rust@gcc.gnu.org>; Fri,  6 Aug 2021 22:39:07 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 66C9F39ADC1B
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 (deer0x03.wildebeest.org [172.31.17.133])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by gnu.wildebeest.org (Postfix) with ESMTPSA id DF2DD30291A9;
 Sat,  7 Aug 2021 00:39:05 +0200 (CEST)
Received: by reform (Postfix, from userid 1000)
 id 74E4B2E80640; Sat,  7 Aug 2021 00:39:05 +0200 (CEST)
Date: Sat, 7 Aug 2021 00:39:05 +0200
From: Mark Wielaard <mark@klomp.org>
To: Philip Herron <philip.herron@embecosm.com>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset
Message-ID: <YQ26CYyY8073ZUlb@wildebeest.org>
References: <20210804151500.BECFC81A9C8@builder.wildebeest.org>
 <YQr31wZAGRigkH1W@wildebeest.org>
 <8b46b6ad-750d-96bf-6814-b0226aa4eaf6@embecosm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8b46b6ad-750d-96bf-6814-b0226aa4eaf6@embecosm.com>
X-Spam-Status: No, score=-5.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 SPF_HELO_NONE, SPF_PASS, TXREP 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: Fri, 06 Aug 2021 22:39:08 -0000

Hi Philip,

On Fri, Aug 06, 2021 at 03:31:07PM +0100, Philip Herron wrote:
> > Is it possible to make bors check all commits in a series? Or can we
> > somehow connect the buildbot workers to the bors checks?
> 
> I think the build-bot checks for every commit is a really nice feature
> here. I think you should keep the build-bots as are. I really like to
> make sure each of my commits are build-able and pass tests. It keeps me
> honest to avoid regressions as best I can.
> 
> What do you think?

I am just a little afraid it is running too late. But I am pretty
happy we have workers for 4 different architectures and they are green
most of the time. We really should add a 32bit (i686 or armhf) one
just to be sure that works correctly.

Currently i686 gets lots of failures like:

/home/mark/gccrs/gcc/testsuite/rust/compile/torture/methods3.rs:27:5: error: type mismatch in binary exp
ression
f64
<float:80>
<float:80>
D.229 = _2 + _4;
/home/mark/gccrs/gcc/testsuite/rust/compile/torture/methods3.rs:27:5: internal compiler error: 'verify_g
imple' failed
0x8b41fd4 verify_gimple_in_seq(gimple*)
        ../../gccrs/gcc/tree-cfg.c:5157
0x884b4c3 gimplify_body(tree_node*, bool)
        ../../gccrs/gcc/gimplify.c:15401
0x884b692 gimplify_function_tree(tree_node*)
        ../../gccrs/gcc/gimplify.c:15472
0x86a6448 cgraph_node::analyze()
        ../../gccrs/gcc/cgraphunit.c:670
0x86a9218 analyze_functions
        ../../gccrs/gcc/cgraphunit.c:1236
0x86a9e01 symbol_table::finalize_compilation_unit()
        ../../gccrs/gcc/cgraphunit.c:2514

Cheers,

Mark