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 BE5753858D32 for ; Sun, 15 May 2022 15:04:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org BE5753858D32 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 188F9302BBEC; Sun, 15 May 2022 17:04:42 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 5B80B2E82EDA; Sun, 15 May 2022 17:04:26 +0200 (CEST) Date: Sun, 15 May 2022 17:04:26 +0200 From: Mark Wielaard To: gdb-testers@sourceware.org Cc: Tom Tromey Subject: Re: =?utf-8?Q?=E2=98=A0_Buildbot_=28GN?= =?utf-8?Q?U?= Toolchain): binutils-gdb - failed test (failure) (master) Message-ID: References: <20220513201818.ECFEB398AC3D@sourceware.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220513201818.ECFEB398AC3D@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: gdb-testers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-testers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 May 2022 15:04:46 -0000 Hi, On Fri, May 13, 2022 at 08:18:18PM +0000, builder@sourceware.org wrote: > A new failure has been detected on builder gdb-debian-armhf while building binutils-gdb. > > Full details are available at: > https://builder.sourceware.org/buildbot/#builders/72/builds/181 > > Build state: failed test (failure) > Revision: 5400535a70cd5f7626f4110a69508ad9ff669328 > Worker: debian-armhf > Build Reason: (unknown) > Blamelist: Tom Tromey > > Steps: > [...] > - 5: make check-gdb ( failure ) > Logs: > - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/181/steps/5/logs/stdio > - gdb.sum: https://builder.sourceware.org/buildbot/#builders/72/builds/181/steps/5/logs/gdb_sum > - gdb.log: https://builder.sourceware.org/buildbot/#builders/72/builds/181/steps/5/logs/gdb_log I was a little afraid of this. It looks like even this simple unittest.exp is slightly flaky. It has failed twice now on armhf (but not on any other arch). The actual failure is an timeout followed by some errors because some variables aren't set after the timeout. (gdb) maintenance selftest Running selftest addrmap. Running selftest arm-record. Running selftest arm_analyze_prologue. Running selftest array_view. Running selftest array_view-copy. Running selftest child_path. Running selftest cli_utils. Running selftest command_structure_invariants. Running selftest complaints. Running selftest copy_bitwise. Running selftest copy_integer_to_size. Running selftest cp_remove_params. Running selftest cp_symbol_name_matches. Running selftest dw2_expand_symtabs_matching. warning: could not convert 'u8função' from the host encoding (ANSI_X3.4-1968) to UTF-32. This normally should not happen, please file a bug report. warning: charset conversion failure for 'u8função'. You may have the wrong value for 'set ada source-charset'. Running selftest dwarf2_find_containing_comp_unit. Running selftest enum-flags. [...] Running selftest string_appendf. Running selftest string_printf. Running selftest string_vappendf. Running selftest string_view. FAIL: gdb.gdb/unittest.exp: no executable loaded: maintenance selftest (timeout) ERROR: tcl error sourcing /var/lib/buildbot/workers/wildebeest/gdb-debian-armhf/gdb-build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.gdb/unittest.exp. ERROR: can't read "num_ran": no such variable while executing "list $enabled $num_ran" (procedure "run_selftests" line 34) invoked from within "run_selftests """ ("uplevel" body line 2) invoked from within "uplevel 1 $body" invoked from within "with_test_prefix "no executable loaded" { set res [run_selftests ""] set self_tests_enabled [lindex $res 0] set num_ran [lindex $res 1] }" (file "/var/lib/buildbot/workers/wildebeest/gdb-debian-armhf/gdb-build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.gdb/unittest.exp" line 89) invoked from within "source /var/lib/buildbot/workers/wildebeest/gdb-debian-armhf/gdb-build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.gdb/unittest.exp" ("uplevel" body line 1) invoked from within "uplevel #0 source /var/lib/buildbot/workers/wildebeest/gdb-debian-armhf/gdb-build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.gdb/unittest.e..." invoked from within "catch "uplevel #0 source $test_file_name"" testcase /var/lib/buildbot/workers/wildebeest/gdb-debian-armhf/gdb-build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.gdb/unittest.exp completed in 19 seconds It is not clear to me why the timeout occurs after "Running selftest string_view." there should be more self tessts coming after that. But the two times it timed out it did after that. Let me know if this get annoying and I remove the selftest from the gdb-check step. Cheers, Mark