From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (wildebeest.demon.nl [212.238.236.112]) by sourceware.org (Postfix) with ESMTPS id 73E4B3938C2C for ; Thu, 11 Jun 2020 16:15:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 73E4B3938C2C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mark@klomp.org Received: from librem (deer0x15.wildebeest.org [172.31.17.151]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 01CBE30447FA; Thu, 11 Jun 2020 18:15:53 +0200 (CEST) Received: by librem (Postfix, from userid 1000) id EBCC7C23AC; Thu, 11 Jun 2020 18:15:22 +0200 (CEST) Date: Thu, 11 Jun 2020 18:15:22 +0200 From: Mark Wielaard To: buildbot@builder.wildebeest.org Cc: elfutils-devel@sourceware.org Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset Message-ID: <20200611161522.GA6605@wildebeest.org> References: <20200611160038.A76A281A9D1@builder.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200611160038.A76A281A9D1@builder.wildebeest.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-7.5 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: elfutils-devel@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Elfutils-devel mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2020 16:15:58 -0000 On Thu, Jun 11, 2020 at 04:00:38PM +0000, buildbot@builder.wildebeest.org wrote: > The Buildbot has detected a failed build on builder whole buildset while building elfutils. > Full details are available at: > https://builder.wildebeest.org/buildbot/#builders/1/builds/546 > > Buildbot URL: https://builder.wildebeest.org/buildbot/ > > Worker for this Build: centos-x86_64 This is a failure in run-debuginfod-find.sh where an extra groom is not happening when expected. I tried to replicate, but failed. Rebuilding the task on the same builder makes it PASS. This doesn't fail on any other buildbot worker. I suspect it is a timing issue with a signal not arriving when expected. But I am not sure. I don't think this should hold up the release, given that is is probably just a testsuite quirk. Cheers, Mark