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 3EA0E3858407 for ; Mon, 6 Sep 2021 15:07:52 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3EA0E3858407 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 tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 13D8B301FE93; Mon, 6 Sep 2021 17:07:50 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 647C84000ABD; Mon, 6 Sep 2021 17:07:50 +0200 (CEST) Message-ID: <31a5a4ff4a158f1e794a28defc30eb14423208ac.camel@klomp.org> Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset From: Mark Wielaard To: buildbot@builder.wildebeest.org Cc: elfutils-devel@sourceware.org Date: Mon, 06 Sep 2021 17:07:50 +0200 In-Reply-To: References: <20210903140840.A291B8026A2@builder.wildebeest.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-4.4 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: 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: Mon, 06 Sep 2021 15:07:54 -0000 On Sat, 2021-09-04 at 01:47 +0200, Mark Wielaard wrote: > On Fri, Sep 03, 2021 at 02:08:40PM +0000,=20 > buildbot@builder.wildebeest.org wrote: > > The Buildbot has detected a new failure on builder elfutils-debian- > > armhf while building elfutils. > > Full details are available at: > > https://builder.wildebeest.org/buildbot/#builders/15/builds/603 > >=20 > > Buildbot URL: https://builder.wildebeest.org/buildbot/ > >=20 > > Worker for this Build: debian-armhf > >=20 > > Build Reason: > > Blamelist: Mark Wielaard > >=20 > > BUILD FAILED: failed test (failure) >=20 > So some of the builders did pass without any failures. But some had > errors, and not all the same ones. I couldn't replicate locally > (everything was green) both with make check and make distcheck. >=20 > But looking at the tests I noticed not all used a clean new cache and > some used the default database. >=20 > So hopefully the attached patch makes things a bit more stable by > explicitly setting the DEBUGINFOD_CACHE_PATH and invoke debuginfod > with a fresh sqlite database. Sadly we still have failures even with this patch: https://builder.wildebeest.org/buildbot/#/changes/2567 The good news is that elfutils-fedora-x86_64, elfutils-fedora-ppc64le, elfutils-fedora-s390x, elfutils-debian-i386, elfutils-fedora-ppc64 and elfutils-debian-armhf are fully green, but... On elfutils-centos-x86_64 make check fails with: FAIL: run-debuginfod-tmp-home.sh FAIL: run-debuginfod-writable.sh On elfutils-debian-arm64 make check fails with: FAIL: run-debuginfod-federation-sqlite.sh On elfutils-centos-x86_64 make check first timed out (!?!) then it failed with: FAIL: run-debuginfod-tmp-home.sh FAIL: run-debuginfod-writable.sh On elfutils-debian-amd64 make check failed with: FAIL: run-debuginfod-archive-groom.sh The failures still look somewhat random (although less random than before). I don't yet know why. Cheers, Mark