Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed 7/7] [gdb/testsuite] Fix test names in gdb.tui/tuiterm.exp
Date: Wed, 14 Oct 2026 16:58:38 +0200	[thread overview]
Message-ID: <20261014145838.3560108-8-tdevries@suse.de> (raw)
In-Reply-To: <20261014145838.3560108-1-tdevries@suse.de>

I noticed an inaccurate test name in gdb.tui/tuiterm.exp.  I asked an LLM to
list locations of other occurrences, and then fixed them.
---
 gdb/testsuite/gdb.tui/tuiterm.exp | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/gdb/testsuite/gdb.tui/tuiterm.exp b/gdb/testsuite/gdb.tui/tuiterm.exp
index 411026457b9..7c3aabaf6ea 100644
--- a/gdb/testsuite/gdb.tui/tuiterm.exp
+++ b/gdb/testsuite/gdb.tui/tuiterm.exp
@@ -207,7 +207,7 @@ proc test_pan_down { } {
 proc test_pan_up { } {
     Term::_move_cursor 1 2
     Term::_csi_T
-    check "pan down, default arg" {
+    check "pan up, default arg" {
 	"        "
 	"abcdefgh"
 	"ijklmnop"
@@ -215,7 +215,7 @@ proc test_pan_up { } {
     } 1 2
 
     Term::_csi_T 2
-    check "pan down, explicit arg" {
+    check "pan up, explicit arg" {
 	"        "
 	"        "
 	"        "
@@ -223,7 +223,7 @@ proc test_pan_up { } {
     } 1 2
 
     Term::_csi_T 100
-    check "pan down, excessive arg" {
+    check "pan up, excessive arg" {
 	"        "
 	"        "
 	"        "
@@ -336,7 +336,7 @@ proc test_cursor_position { } {
     Term::_move_cursor 1 1
 
     Term::_csi_H 3 5
-    check "cursor horizontal absolute 2" $::small_initial 4 2
+    check "cursor position absolute" $::small_initial 4 2
 
     Term::_csi_H 10 10
     check "cursor position absolute, out of bounds" $::small_initial 7 3
-- 
2.51.0


      parent reply	other threads:[~2026-10-14 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 14:58 [pushed 0/7] [gdb/testsuite] Tuiterm maintenance Tom de Vries
2026-10-14 14:58 ` [pushed 1/7] [gdb/testsuite] Remove unused declarations in lib/tuiterm.exp Tom de Vries
2026-10-14 14:58 ` [pushed 2/7] [gdb/testsuite] Factor out Term::_copy_line Tom de Vries
2026-10-14 14:58 ` [pushed 3/7] [gdb/testsuite] Factor out small_initial in gdb.tui/tuiterm.exp Tom de Vries
2026-10-14 14:58 ` [pushed 4/7] [gdb/testsuite] Add Term::check_size Tom de Vries
2026-10-14 14:58 ` [pushed 5/7] [gdb/testsuite] Work around namespace problem in tclint plugin Tom de Vries
2026-10-14 14:58 ` [pushed 6/7] [gdb/testsuite] Fix typo in tclint-plugin.py Tom de Vries
2026-10-14 14:58 ` Tom de Vries [this message]

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=20261014145838.3560108-8-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