From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 74645 invoked by alias); 21 Feb 2020 12:10:20 -0000 Mailing-List: contact elfutils-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: elfutils-devel-owner@sourceware.org Received: (qmail 72966 invoked by uid 89); 21 Feb 2020 12:10:19 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-18.0 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,RCVD_IN_BL_SPAMCOP_NET,SPF_PASS autolearn=ham version=3.3.1 spammy=H*F:U*mark, sk:buildbo, our X-Spam-Status: No, score=-18.0 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,RCVD_IN_BL_SPAMCOP_NET,SPF_PASS autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (212.238.236.112) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 21 Feb 2020 12:10:17 +0000 Received: from tarox.wildebeest.org (tarox.wildebeest.org [172.31.17.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 113C530003A6; Fri, 21 Feb 2020 13:10:14 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 96CEA400B8DB; Fri, 21 Feb 2020 13:10:14 +0100 (CET) Message-ID: <9fe601da261c825c60e3a09d7befa7d291c1f384.camel@klomp.org> Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset From: Mark Wielaard To: buildbot@builder.wildebeest.org, elfutils-devel@sourceware.org Date: Fri, 21 Feb 2020 12:10:00 -0000 In-Reply-To: <20200210223415.3441681A9FD@builder.wildebeest.org> References: <20200210223415.3441681A9FD@builder.wildebeest.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-5.el7) Mime-Version: 1.0 X-Spam-Flag: NO X-IsSubscribed: yes X-SW-Source: 2020-q1/txt/msg00121.txt On Mon, 2020-02-10 at 22:34 +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/15/builds/269 This is a somewhat older failure and newer ones did show all green. I didn't see the fix being posted to the list, so just for the record here it is: commit 990955ef0a320a73ed583246f23d5f220e5916f8 Author: Frank Ch. Eigler Date: Mon Feb 10 14:33:54 2020 -0500 debuginfod testing: SIGUSR2 vs "groom" metric synch =20=20=20=20 Previous code did not account for a groom job that was already completed at startup, so the SIGUSR2-triggered one may not have completed in time for the test. The shell won the race condition on most buildbot VMs, but a debian builder showed the error of our ways. =20=20=20=20 Signed-off-by: Frank Ch. Eigler diff --git a/tests/run-debuginfod-find.sh b/tests/run-debuginfod-find.sh index 939826cd..1cc8f406 100755 --- a/tests/run-debuginfod-find.sh +++ b/tests/run-debuginfod-find.sh @@ -269,7 +269,8 @@ RPM_BUILDID=3Dd44d42cbd7d915bc938c81333a21e355a6022fb7 = # in rhel6/ subdir, for a l rm -r R/debuginfod-rpms/rhel6/* kill -USR2 $PID1 # groom cycle # Expect 3 rpms to be deleted by the groom -wait_ready $PORT1 'thread_work_total{role=3D"groom"}' 1 +# 1 groom already took place at/soon-after startup, so -USR2 makes 2 +wait_ready $PORT1 'thread_work_total{role=3D"groom"}' 2 wait_ready $PORT1 'groom{statistic=3D"file d/e"}' 3 =20 rm -rf $DEBUGINFOD_CACHE_PATH # clean it from previous tests