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 1954F385DC27
 for <gcc-rust@gcc.gnu.org>; Tue, 25 Jan 2022 22:42:44 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1954F385DC27
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 (deer0x12.wildebeest.org [172.31.17.148])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by gnu.wildebeest.org (Postfix) with ESMTPSA id F29E5302FB94;
 Tue, 25 Jan 2022 23:42:41 +0100 (CET)
Received: by reform (Postfix, from userid 1000)
 id 4E0462E80718; Tue, 25 Jan 2022 23:42:41 +0100 (CET)
Date: Tue, 25 Jan 2022 23:42:41 +0100
From: Mark Wielaard <mark@klomp.org>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-rust@gcc.gnu.org, Marc =?iso-8859-1?Q?Poulhi=E8s?= <dkm@kataplop.net>
Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset
Message-ID: <YfB84VtEMCHvAOk+@wildebeest.org>
References: <20220124122958.6E3378003E3@builder.wildebeest.org>
 <fa6dd782c54f54e04128f822ada076553f34f568.camel@klomp.org>
 <87r18wkej6.fsf@arrakis.kataplop.net>
 <871r0wuv4x.fsf@euler.schwinge.homeip.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <871r0wuv4x.fsf@euler.schwinge.homeip.net>
X-Spam-Status: No, score=-4.0 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: Tue, 25 Jan 2022 22:42:45 -0000

Hi,

On Tue, Jan 25, 2022 at 08:33:50AM +0100, Thomas Schwinge wrote:
> On 2022-01-24T22:30:21+0100, Marc via Gcc-rust <gcc-rust@gcc.gnu.org> wrote:
> > Mark Wielaard <mark@klomp.org> writes:
> >> Sorry, I don't immediately know what is happening.
> >> I assume some merge took place and the buildbot doesn't know what are
> >> good/bad commits and just tries to do builds for everything in the
> >> merge. I have shutdown the buildbot till I have time to figure out what
> >> is going on.
> >
> > Yes, it seems Thomas did a merge in
> > 21af490baa734a901fb798bc2ac4df62109bc895, bringing gcc's master from a
> > few days back :) [490e23032baaece71f2ec09fa1805064b150fbc2]
> 
> Yes, I did.  Mark, should I announce that in advance from now on?

I added a filesIsImportant filter to the buildbot gccrs scheduler:

gccrs_files = ["gcc/rust/", "gcc/testsuite/rust/", "gcc/config/.*/*-rust.c"]

def gccrsImportant(change):
    for file in change.files:
        for pattern in gccrs_files:
            match = re.match(pattern, file)
            if match:
                return True
    return False

I think that should make sure that in the future any commits that
aren't part of the gccrs frontend won't trigger a build.

Cheers,

Mark