public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] gdb/testsuite: Avoid leaking a port number into results summary
Date: Thu, 06 Feb 2020 19:07:00 -0000	[thread overview]
Message-ID: <b0999b9b4574371f4b7682d0ccf5f7dbf1702262@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT b0999b9b4574371f4b7682d0ccf5f7dbf1702262 ***

commit b0999b9b4574371f4b7682d0ccf5f7dbf1702262
Author:     Andrew Burgess <andrew.burgess@embecosm.com>
AuthorDate: Thu Feb 6 16:37:10 2020 +0000
Commit:     Andrew Burgess <andrew.burgess@embecosm.com>
CommitDate: Thu Feb 6 16:39:20 2020 +0000

    gdb/testsuite: Avoid leaking a port number into results summary
    
    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

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index eb4388031b..793a0af630 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -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.
diff --git a/gdb/testsuite/gdb.server/multi-ui-errors.exp b/gdb/testsuite/gdb.server/multi-ui-errors.exp
index c2a05b0fb6..9d64a9a245 100644
--- a/gdb/testsuite/gdb.server/multi-ui-errors.exp
+++ b/gdb/testsuite/gdb.server/multi-ui-errors.exp
@@ -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"
 }
 


             reply	other threads:[~2020-02-06 18:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 19:07 gdb-buildbot [this message]
2020-02-06 19:08 ` Failures on Fedora-i686, branch master gdb-buildbot
2020-02-06 19:15 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2020-02-06 19:21 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2020-02-06 19:40 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2020-02-06 20:16 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-02-06 20:39 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-02-06 21:25 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2020-02-06 23:17 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot

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=b0999b9b4574371f4b7682d0ccf5f7dbf1702262@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).