public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: gdb-testers@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed test (failure) (master)
Date: Sun, 15 May 2022 17:04:26 +0200	[thread overview]
Message-ID: <YoEWerF7cNXxvOGy@wildebeest.org> (raw)
In-Reply-To: <20220513201818.ECFEB398AC3D@sourceware.org>

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 <tromey@adacore.com>
> 
> 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



  reply	other threads:[~2022-05-15 15:04 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 20:18 builder
2022-05-15 15:04 ` Mark Wielaard [this message]
2022-05-16  8:25   ` Luis Machado
2022-05-16  8:44     ` Mark Wielaard
2022-05-16  9:12       ` Luis Machado
2022-05-15  0:25 builder
2022-05-17  5:52 builder
2022-05-17 10:50 builder
2022-05-18  0:23 builder
2022-05-18 13:02 builder
2022-05-18 13:45 ` Mark Wielaard
2022-05-18 16:30   ` Luis Machado
2022-05-31 15:39 builder
2022-06-07 18:34 builder
2022-07-08 14:07 builder
2022-07-15  0:19 builder
2022-07-15 17:52 builder
2022-07-19 14:54 builder
2022-07-29  7:49 builder
2022-07-30  0:27 builder
2022-08-03 20:03 builder
2022-08-31 17:30 builder
2022-08-31 18:22 builder
2022-09-12  8:31 builder
2022-09-13 12:20 builder
2022-10-16 17:05 builder
2022-10-16 17:15 builder
2022-10-16 17:19 builder
2022-10-16 17:23 builder
2022-10-16 17:23 builder
2022-10-16 17:51 builder
2022-10-16 18:51 builder
2022-10-16 19:01 builder
2022-10-18 15:33 builder
2022-10-26  7:45 builder
2022-10-26 12:16 builder
2022-11-07 16:53 builder
2022-11-11 15:20 builder
2022-11-22  0:29 builder
2022-11-28 16:18 builder
2022-11-28 16:22 builder
2022-12-06 15:13 builder
2022-12-15  0:31 builder
2022-12-22  4:09 builder
2023-01-11  1:01 builder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YoEWerF7cNXxvOGy@wildebeest.org \
    --to=mark@klomp.org \
    --cc=gdb-testers@sourceware.org \
    --cc=tromey@adacore.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).