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 785443857C45 for ; Mon, 21 Aug 2023 08:57:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 785443857C45 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: by gnu.wildebeest.org (Postfix, from userid 1000) id 62BB2302BBEC; Mon, 21 Aug 2023 10:57:56 +0200 (CEST) Date: Mon, 21 Aug 2023 10:57:56 +0200 From: Mark Wielaard To: Jan Beulich Cc: Sam James , Binutils Subject: Re: =?utf-8?B?4pigIEJ1aWxkYm8=?= =?utf-8?Q?t?= (Sourceware): binutils-gdb - failed test (failure) (master) Message-ID: <20230821085756.GF16919@gnu.wildebeest.org> References: <20230818215458.6F9403858D32@sourceware.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-3029.5 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Jan (added Sam to CC), On Mon, Aug 21, 2023 at 08:25:23AM +0200, Jan Beulich wrote: > On 18.08.2023 23:54, builder@sourceware.org wrote: > > A new failure has been detected on builder binutils-gentoo-sparc while building binutils-gdb. > > > > Full details are available at: > > https://builder.sourceware.org/buildbot/#builders/228/builds/1142 > > > > Build state: failed test (failure) > > Revision: b41ef0baac449de58c84d1a0261af0d91443b540 > > Worker: gentoo-sparc > > Build Reason: (unknown) > > Blamelist: Jan Beulich > > > > Steps: > [...] > > - 5: make check ( failure ) > > Logs: > > - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/1142/steps/5/logs/stdio > > Looking just here - where's the failure indication, other than an unhelpful > "timed out"? (I believe this isn't the first time I'm observing such a > report.) Clearly something hung in the testsuite. Sometimes you can find additional logs in the full build steps here: https://builder.sourceware.org/buildbot/#builders/228/builds/1142 And if that doesn't give a clue (it doesn't in this case), you can look for the Upload to bunsen step, which contains an URL to the bunsen entry containing all log files and full results, in this case: https://builder.sourceware.org/testrun/02dd95c110a6d72025efd682e0614fac3bd7ee13 The filelist normally contains some logs that can be helpful. But I don't see anything specific in this case either. So then we ask the person running the buildbot sparc builder, which is Sam (CCed). All the builds after this one seem green. So maybe the buildbot worker was just really slow? Cheers, Mark