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 16AFA38582A7; Mon, 4 Jul 2022 15:17:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 16AFA38582A7 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 E41DF302AB2C; Mon, 4 Jul 2022 17:17:55 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 65FFC404AC7E; Mon, 4 Jul 2022 17:17:55 +0200 (CEST) Message-ID: <5763f0b8f4c255855996e3fdc39ff72808775e5a.camel@klomp.org> Subject: Re: glibc builder.sourceware.org integration From: Mark Wielaard To: libc-alpha@sourceware.org Cc: buildbot@sourceware.org Date: Mon, 04 Jul 2022 17:17:55 +0200 In-Reply-To: References: 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=-5.7 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: buildbot@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "The https://builder.sourceware.org/ buildbot" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jul 2022 15:17:58 -0000 Hi, On Sat, 2022-07-02 at 00:24 +0200, Mark Wielaard wrote: > On Fri, Jul 01, 2022 at 02:00:42PM +0200, Mark Wielaard wrote: > > For now I have added a make subdirs=3Delf -jncpus check step. This > > seems to have a couple of hundred tests which should be quick > > enough > > to run on all builders. Test results are uploaded to the bunsendb > > for > > comparison between distr/arches. Builders all seem to be green > > (except > > for the full testrun builders of course), but the glibc-fedora- > > ppc64le builder has one FAIL: > > FAIL: elf/tst-ldconfig-bad-aux-cache > > https://builder.sourceware.org/buildbot/#/builders?tags=3Dglibc > > https://builder.sourceware.org/buildbot/#/builders/127/builds/35 > >=20 > > Frank, I cannot find the corresponding bunsen test results for that > > build under https://builder.sourceware.org/testruns/ did I make a > > mistake in the bunsen upload step? >=20 > It is there now. I don't know why it wasn't there earlier. Frank, is > there a delay between the bunsendb update and when the testruns show > up? > https://builder.sourceware.org/testrun/deda118447159c9affe00348cfb1ddf667= 563fe4 >=20 > Which also contains the tst-ldconfig-bad-aux-cache.out file > https://builder.sourceware.org/testrun/deda118447159c9affe00348cfb1ddf667= 563fe4?filename=3Delf%2Ftst-ldconfig-bad-aux-cache.out >=20 > Timed out: killed the child process >=20 > I couldn't immediately replicate that on a ppc64le setup. > Lets see if a next build also causes this test to time out. It was only that one build. All others are green: https://builder.sourceware.org/buildbot/#/builders/glibc-fedora-ppc64le I haven't figured out or have been able to replicate this issue. The test runs ldconfig with a corrupt aux-cache and checks it doesn't crash. Maybe instead of crashing sometimes ldconfig goes into a loop? Cheers, Mark