[PUSHED] gdb/testsuite: don't include port numbers in test names

Message ID b5c7f1fd7b9459bbd8b79e7e968aa56b42ff980c.1711751470.git.aburgess@redhat.com
State New
Headers
Series [PUSHED] gdb/testsuite: don't include port numbers in test names |

Checks

Context Check Description
linaro-tcwg-bot/tcwg_gdb_build--master-aarch64 warning Patch is already merged
linaro-tcwg-bot/tcwg_gdb_build--master-arm warning Patch is already merged

Commit Message

Andrew Burgess March 29, 2024, 10:31 p.m. UTC
  The gdb.python/py-cmd-prompt.exp script includes a test that has a
gdbserver port number within a test name.  As port numbers can change
from one test run to the next (depending on what else is running on
the machine at the time), this can make it hard to compare test
results between runs.

Give the test a specific name to avoid including the port number.

There is no change in what is tested after this commit.
---
 gdb/testsuite/gdb.python/py-cmd-prompt.exp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)


base-commit: 43f8b6e2578a76fd96bf08172b2ea6fdcaf6c2e4
  

Patch

diff --git a/gdb/testsuite/gdb.python/py-cmd-prompt.exp b/gdb/testsuite/gdb.python/py-cmd-prompt.exp
index a69211ce33d..ccb695f6638 100644
--- a/gdb/testsuite/gdb.python/py-cmd-prompt.exp
+++ b/gdb/testsuite/gdb.python/py-cmd-prompt.exp
@@ -39,7 +39,8 @@  gdb_test_no_output "source $pyfile" "source the script"
 
 set gdbserver [gdbserver_start "" [standard_output_file $binfile]]
 set gdbserver_gdbport [lindex $gdbserver 1]
-gdb_test_no_output "python the_listener.port = '${gdbserver_gdbport}'"
+gdb_test_no_output "python the_listener.port = '${gdbserver_gdbport}'" \
+    "set the_listener.port value"
 
 gdb_run_cmd