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 3A49E3858425 for ; Sun, 12 Sep 2021 22:30:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3A49E3858425 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 (deer0x0b.wildebeest.org [172.31.17.141]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 065CC30006CF; Mon, 13 Sep 2021 00:30:36 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 828CB2E806B8; Mon, 13 Sep 2021 00:30:36 +0200 (CEST) Date: Mon, 13 Sep 2021 00:30:36 +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: References: <20210912215639.1D24F80EA29@builder.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210912215639.1D24F80EA29@builder.wildebeest.org> X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_BADIPHTTP, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: Sun, 12 Sep 2021 22:30:40 -0000 Hi, On Sun, Sep 12, 2021 at 09:56:39PM +0000, buildbot@builder.wildebeest.org wrote: > The Buildbot has detected a new failure on builder elfutils-centos-x86_64 while building elfutils. > Full details are available at: > https://builder.wildebeest.org/buildbot/#builders/1/builds/835 > > Buildbot URL: https://builder.wildebeest.org/buildbot/ > > Worker for this Build: centos-x86_64 > > Build Reason: > Blamelist: Colin Cross > > BUILD FAILED: failed test (failure) > [...] > Full details are available at: > https://builder.wildebeest.org/buildbot/#builders/12/builds/777 This is certainly not caused by Colin's patch. It is the same failure on two different systems, in related, but different tests. run-debuginfod-federation-link.sh run-debuginfod-federation-metrics.sh run-debuginfod-federation-sqlite.sh All have the following subtest: # confirm that first server can't resolve symlinked info in L/ but second can BUILDID=`env LD_LIBRARY_PATH=$ldpath ${abs_builddir}/../src/readelf \ -a L/foo | grep 'Build ID' | cut -d ' ' -f 7` file L/foo file -L L/foo export DEBUGINFOD_URLS=http://127.0.0.1:$PORT1 rm -rf $DEBUGINFOD_CACHE_PATH testrun ${abs_top_builddir}/debuginfod/debuginfod-find debuginfo $BUILDID && false || true rm -f $DEBUGINFOD_CACHE_PATH/$BUILDID/debuginfo # drop 000-perm negative-hit file export DEBUGINFOD_URLS=http://127.0.0.1:$PORT2 testrun ${abs_top_builddir}/debuginfod/debuginfod-find debuginfo $BUILDID Where L/foo is created with: ln -s ${abs_builddir}/dwfllines L/foo # any program not used elsewhere in this test Both debuginfod servers have L in their scan path, but only the one on PORT2 has -L L. So the one on PORT1 should not resolve the foo symlink, but the one on PORT2 doesn't. For some reason it seems even the server on PORT2 doesn't record L/foo sometimes (but not always). I haven't figured out why. Both failures above have extended logs, so maybe someone else can figure out what is going wrong in the failure case? https://builder.wildebeest.org/buildbot/#/builders/12/builds/777/steps/8/logs/test-suite_log https://builder.wildebeest.org/buildbot/#/builders/1/builds/835/steps/8/logs/test-suite_log Cheers, Mark