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 B28F83858C53 for ; Wed, 2 Nov 2022 14:19:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B28F83858C53 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 A92573061FA5 for ; Wed, 2 Nov 2022 15:19:18 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 8BB82413CD0E; Wed, 2 Nov 2022 15:19:17 +0100 (CET) Message-ID: <2795ea045a9fcc90220d2164c551c607eed15fef.camel@klomp.org> Subject: Re: =?UTF-8?Q?=E2=98=A0?= Buildbot (GNU Toolchain): elfutils - failed test (failure) (master) From: Mark Wielaard To: elfutils-devel@sourceware.org Date: Wed, 02 Nov 2022 15:19:17 +0100 In-Reply-To: <20221102133920.439BB3858C50@sourceware.org> References: <20221102133920.439BB3858C50@sourceware.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=-3033.1 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.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi, On Wed, 2022-11-02 at 13:39 +0000, builder--- via Elfutils-devel wrote: > A new failure has been detected on builder elfutils-centos-x86_64 > while building elfutils. >=20 > Full details are available at: > https://builder.sourceware.org/buildbot/#builders/39/builds/99 >=20 > Build state: failed test (failure) > Revision: e9f3045caa5c4498f371383e5519151942d48b6d > Worker: centos-x86_64 > Build Reason: (unknown) > Blamelist: Mark Wielaard >=20 > Steps: > [...] > https://builder.sourceware.org/buildbot/#builders/39/builds/99/steps/6/lo= gs/warnings__2_ >=20 > - 7: make check ( failure ) > Logs: > - stdio:=20 > https://builder.sourceware.org/buildbot/#builders/39/builds/99/steps/7/lo= gs/stdio > - test-suite.log:=20 > https://builder.sourceware.org/buildbot/#builders/39/builds/99/steps/7/lo= gs/test-suite_log So this is run-backtrace-native-core-biarch.sh which only occasionally fails. It also fails on on debian-testing. It looks like the pc is off when the core file is generated, which might be a kernel issue, but I don't understand why it only happens sometimes. Might be because there are two threads running? It seems we have two tests that occasionally fail. Which is not good. But also not that bad that it should stop the release imho. Cheers, Mark