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 5D85C384A8A6 for ; Fri, 10 Sep 2021 13:14:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5D85C384A8A6 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 87AB83000EF9 for ; Fri, 10 Sep 2021 15:14:33 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 1FED84000A90; Fri, 10 Sep 2021 15:14:32 +0200 (CEST) Message-ID: Subject: buildbot status From: Mark Wielaard To: elfutils-devel@sourceware.org Date: Fri, 10 Sep 2021 15:14:32 +0200 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.3 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: Fri, 10 Sep 2021 13:14:40 -0000 Hi, Since the splitting of the mega debuginfod tests into separate testcases we have seen some instability of the buildbot. I believe that is mostly solved now. I do sometimes see one of the run-debuginfod-federation- {link,metric,sqlite}.sh tests fail when they are testing propagating of a client request between servers when the request is for some symlinked debuginfo. But when I showed that to Frank he immediately said that the shell logic for that test was bogus, so I am hoping that when he cleans that up that also gets rid of the false positives. At least we should now get better error reports when something fails (previously a runtest that failed, but not a normal shell command, would simply cleanup instead of spitting out the metrics and server logs). There also seems to be a spurious fail of the native core backtrace test on centos-x86_64. I looked at it, but cannot really figure it out. When it fails we believe to be in __clone inside libc.so.6 but at a pc that doesn't have cfi, so we cannot unwind. Maybe this is simply a bug in either the core file writing under centos7 or glibc really is missing some cfi for clone. But that doesn't explain why it is non- deterministic. Finally things took a really long time because most buildbot workers were doing a full distcheck, which involves a normal build, a normal make check, generating a dist tar ball, unpacking it again, valgrind, the gcc undefined sanitizer, a srcdir =3D=3D builddir, a srcdir !=3D builddir, an install check and another build check. On some builders this took more than an hour. And for some reason the s390x builder was so slow that it took 6 hours (!) for each commit. So I have reconfigured the builders a bit: - Only elfutils-fedora-x86_64 does a full distcheck - elfutils-centos-x86_64, elfutils-debian-amd64, elfutils-debian-i386, elfutils-fedora-ppc64le and elfutils-fedora-s390x configure --enable-valgrind --enable-sanitize-undefined and do a make && make check - elfutils-debian-arm64 configure --enable-valgrind && make && make check - elfutils-fedora-ppc64 and elfutils-debian-armhf configure without valgrind and sanitizer and simply make && make check Hopefully that gives us buildbot results a bit quicker. Cheers, Mark