From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/testsuite] Require allow_tui_tests in gdb.tui/new-ui.exp
Date: Mon, 3 Aug 2026 19:03:38 +0200 [thread overview]
Message-ID: <20260803170338.2778730-1-tdevries@suse.de> (raw)
I build gdb without TUI support, and ran into:
...
FAIL: gdb.tui/new-ui.exp: main-ui: new-ui tui $new_ui_tty_name
...
Fix this by requiring allow_tui_tests.
---
gdb/testsuite/gdb.tui/new-ui.exp | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gdb/testsuite/gdb.tui/new-ui.exp b/gdb/testsuite/gdb.tui/new-ui.exp
index 8fe3567077a..e6c6409e233 100644
--- a/gdb/testsuite/gdb.tui/new-ui.exp
+++ b/gdb/testsuite/gdb.tui/new-ui.exp
@@ -15,6 +15,8 @@
# Test TUI in combination with a new UI.
+require allow_tui_tests
+
tuiterm_env
# Creating a pty is done on build, and we use it with gdb on host, so we need
base-commit: 23ee11771f16449e384ada7a0de83722aaceafcf
--
2.51.0
reply other threads:[~2026-08-03 17:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260803170338.2778730-1-tdevries@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
/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