gdb/testsuite: Avoid leaking a port number into results summary
authorAndrew Burgess <andrew.burgess@embecosm.com>
Thu, 6 Feb 2020 16:37:10 +0000 (16:37 +0000)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Thu, 6 Feb 2020 16:39:20 +0000 (16:39 +0000)
Give a test a real name in order to avoid including a port number in
the results summary file - which makes comparing test results between
runs hard.

gdb/testsuiteChangeLog:

* gdb.server/multi-ui-errors.exp: Give a test a real name to avoid
including a port number in the output.

Change-Id: I19334e176ac15aee2a9732a6060c58153d9fb793

gdb/testsuite/ChangeLog
gdb/testsuite/gdb.server/multi-ui-errors.exp

index eb4388031b5449cc5dcf3b2efa55ad904da3c6f3..793a0af630cd9a32620a6c20c88e307b1b151892 100644 (file)
@@ -1,3 +1,8 @@
+2020-02-06  Andrew Burgess  <andrew.burgess@embecosm.com>
+
+       * gdb.server/multi-ui-errors.exp: Give a test a real name to avoid
+       including a port number in the output.
+
 2020-02-04  Alok Kumar Sharma  <alokkumar.sharma@amd.com>
 
        * lib/fortran.exp (fortran_int4): Handle clang.
index c2a05b0fb6f2090d6f6e2f96df6246f8e14202b7..9d64a9a245bc3829d57b2eccf92e1918ef2c57fa 100644 (file)
@@ -65,7 +65,8 @@ with_spawn_id $extra_spawn_id {
 
 # Connect to the remote and continue its execution from the other UI.
 with_spawn_id $extra_spawn_id {
-    gdb_test "target $gdbserver_protocol $gdbserver_gdbport" ".*"
+    gdb_test "target $gdbserver_protocol $gdbserver_gdbport" ".*" \
+       "connect to gdbserver"
     send_gdb "continue\n"
 }