From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 0/8] [gdb/testsuite] Fix timeouts in TUI tests
Date: Thu, 13 Apr 2023 16:08:19 +0200 [thread overview]
Message-ID: <20230413140827.19412-1-tdevries@suse.de> (raw)
Add a warning for timeout in accept_gdb_output.
With the current state, that gives the following warnings:
...
Running gdb.tui/regs.exp ...
Running gdb.tui/resize.exp ...
Running gdb.tui/tui-nl-filtered-output.exp ...
Running gdb.python/tui-window-factory.exp ...
Running gdb.tui/break.exp ...
Running gdb.tui/new-layout.exp ...
WARNING: timeout in accept_gdb_output
Running gdb.tui/winwidth.exp ...
Running gdb.tui/tui-focus.exp ...
Running gdb.tui/info-win.exp ...
Running gdb.python/tui-window-names.exp ...
Running gdb.tui/tuiterm.exp ...
Running gdb.tui/basic.exp ...
Running gdb.tui/completion.exp ...
WARNING: timeout in accept_gdb_output
Running gdb.tui/tui-layout-asm.exp ...
Running gdb.tui/corefile-run.exp ...
WARNING: timeout in accept_gdb_output
Running gdb.python/tui-window-disabled.exp ...
Running gdb.tui/list-before.exp ...
Running gdb.tui/list.exp ...
Running gdb.tui/tui-layout.exp ...
Running gdb.tui/tui-layout-asm-short-prog.exp ...
Running gdb.tui/tui-disasm-long-lines.exp ...
Running gdb.tui/main.exp ...
WARNING: timeout in accept_gdb_output
Running gdb.tui/tui-missing-src.exp ...
Running gdb.python/tui-window.exp ...
Running gdb.tui/winheight.exp ...
Running gdb.tui/scroll.exp ...
Running gdb.tui/empty.exp ...
WARNING: timeout in accept_gdb_output
...
This series fixes all the timeouts.
The series also proposes a fix for PR tui/30337, a problem I ran into while
fixing the timeout in gdb.tui/empty.exp.
The patches fixing gdb.tui/empty.exp and PR30337 could be merged, but I prefer
to keep them seperate, to allow the former to be backported without the latter.
Tested on x86_64-linux.
Tom de Vries (8):
[gdb/testsuite] Add warning for timeout in accept_gdb_output
[gdb/testsuite] Add debug prints in Term::wait_for
[gdb/testsuite] Fix timeout in gdb.tui/corefile-run.exp
[gdb/testsuite] Fix timeout in gdb.tui/main.exp
[gdb/testsuite] Fix timeout in gdb.tui/new-layout.exp
[gdb/testsuite] Fix timeout in gdb.tui/completion.exp
[gdb/testsuite] Fix timeout in gdb.tui/empty.exp
[gdb/tui] Fix TUI for TERM=ansi
gdb/testsuite/gdb.tui/completion.exp | 2 +-
gdb/testsuite/gdb.tui/corefile-run.exp | 3 ++-
gdb/testsuite/gdb.tui/main.exp | 3 ++-
gdb/testsuite/lib/tuiterm.exp | 35 +++++++++++++++++++-------
gdb/tui/tui-win.c | 3 +++
gdb/utils.c | 9 +++++++
gdb/utils.h | 7 ++++++
7 files changed, 50 insertions(+), 12 deletions(-)
base-commit: 546c7898dccb204eb56c8ed7c5b707c75de31b53
--
2.35.3
next reply other threads:[~2023-04-13 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 14:08 Tom de Vries [this message]
2023-04-13 14:08 ` [PATCH 1/8] [gdb/testsuite] Add warning for timeout in accept_gdb_output Tom de Vries
2023-04-13 14:08 ` [PATCH 2/8] [gdb/testsuite] Add debug prints in Term::wait_for Tom de Vries
2023-04-13 14:08 ` [PATCH 3/8] [gdb/testsuite] Fix timeout in gdb.tui/corefile-run.exp Tom de Vries
2023-04-13 14:08 ` [PATCH 4/8] [gdb/testsuite] Fix timeout in gdb.tui/main.exp Tom de Vries
2023-04-13 14:08 ` [PATCH 5/8] [gdb/testsuite] Fix timeout in gdb.tui/new-layout.exp Tom de Vries
2023-04-13 14:08 ` [PATCH 6/8] [gdb/testsuite] Fix timeout in gdb.tui/completion.exp Tom de Vries
2023-04-13 14:08 ` [PATCH 7/8] [gdb/testsuite] Fix timeout in gdb.tui/empty.exp Tom de Vries
2023-04-13 14:08 ` [PATCH 8/8] [gdb/tui] Fix TUI for TERM=ansi Tom de Vries
2023-04-13 14:17 ` Tom de Vries
2023-04-14 11:02 ` Tom de Vries
2023-04-18 6:10 ` Tom de Vries
2023-04-25 7:09 ` Tom de Vries
2023-04-30 11:08 ` Tom de Vries
2023-04-25 6:35 ` [PATCH 0/8] [gdb/testsuite] Fix timeouts in TUI tests Tom de Vries
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=20230413140827.19412-1-tdevries@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).