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 8EFBC3858C52 for ; Sat, 14 May 2022 16:40:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8EFBC3858C52 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 (deer0x07.wildebeest.org [172.31.17.137]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 9731C302BBEC for ; Sat, 14 May 2022 18:40:17 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 56CC52E80832; Sat, 14 May 2022 18:40:01 +0200 (CEST) Date: Sat, 14 May 2022 18:40:01 +0200 From: Mark Wielaard To: elfutils-devel@sourceware.org Subject: Re: =?utf-8?B?4pigIEJ1aWxkYm8=?= =?utf-8?Q?t?= (GNU Toolchain): elfutils - failed test (failure) (master) Message-ID: References: <20220514153443.C670F3858430@sourceware.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220514153443.C670F3858430@sourceware.org> X-Spam-Status: No, score=-3.5 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: 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: Sat, 14 May 2022 16:40:21 -0000 Hi, On Sat, May 14, 2022 at 03:34:43PM +0000, builder--- via Elfutils-devel wrote: > A new failure has been detected on builder elfutils-debian-armhf while building elfutils. > > Full details are available at: > https://builder.sourceware.org/buildbot/#builders/6/builds/27 > > Build state: failed test (failure) > Revision: 0f2c8af3ba82ac54acc63ab7cb068578a6c0d96e > Worker: debian-armhf > Build Reason: (unknown) > Blamelist: Mark Wielaard > > Steps: > [...] > - 7: make check ( failure ) > Logs: > - stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/27/steps/7/logs/stdio > - test-suite.log: https://builder.sourceware.org/buildbot/#builders/6/builds/27/steps/7/logs/test-suite_log This failed twice today: FAIL: run-backtrace-native-core.sh ================================== 0xbeff4000 0xbeff5000 linux-vdso.so.1 0xb6fa9000 0xb6fd2974 ld-linux-armhf.so.3 0xb62a7000 0xb6321078 libm.so.6 0xb6322000 0xb642c6ec libstdc++.so.6 0xb642d000 0xb6442218 librt.so.1 0xb6443000 0xb64550c4 libdl.so.2 0xb6456000 0xb654f33c libc.so.6 0xb6550000 0xb6574270 libpthread.so.0 0xb6575000 0xb659d134 libgcc_s.so.1 0xb659e000 0xb6a4c0f4 libubsan.so.1 0xb6a4d000 0xb6fa8e30 libasan.so.5 0x4a0000 0x4b27c0 backtrace-child TID 25528: # 0 0xb655f526 __libc_do_syscall # 1 0xb655e316 - 1 raise # 2 0x4a1290 - 1 sigusr2 # 3 0x4a1344 - 1 stdarg # 4 0x4a1378 - 1 backtracegen # 5 0x4a1382 - 1 start # 6 0xb6555bbe - 1 start_thread # 7 0xb64f016c - 1 TID 25526: # 0 0xb64ed8d2 syscall # 1 0xb6a89adc - 1 __interceptor_pthread_create /var/lib/buildbot/workers/wildebeest/elfutils-debian-armhf/build/tests/backtrace: dwfl_thread_getframes: no matching address range /var/lib/buildbot/workers/wildebeest/elfutils-debian-armhf/build/tests/backtrace: dwfl_thread_getframes: No DWARF information found backtrace: backtrace.c:81: callback_verify: Assertion `seen_main' failed. ./test-subr.sh: line 84: 25578 Aborted LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH" $VALGRIND_CMD "$@" /var/lib/buildbot/workers/wildebeest/elfutils-debian-armhf/build/tests/backtrace: dwfl_thread_getframes: No DWARF information found backtrace-child-core.25526: arm needs debuginfo installed for all libraries rmdir: failed to remove 'test-25518': Directory not empty FAIL run-backtrace-native-core.sh (exit status: 1) And once last week. Sadly I don't know why. If this test keep being flaky on armhf then we might have to disable it. Since this seems to be compiled with ubsan and asan I installed the libasan5-dbg and libasan5-dbg packages. Maybe that helps. Cheers, Mark