Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [obv] testsuite: Fix `help thread find`
Date: Sat, 05 Mar 2011 13:17:00 -0000	[thread overview]
Message-ID: <20110305131701.GA1017@host1.jankratochvil.net> (raw)

Hi,

I do not know why but it was causing random:

 PASS: gdb.base/help.exp: help
-FAIL: gdb.base/help.exp: help thread name
+PASS: gdb.base/help.exp: help thread name

In the common case it will:
-PASS: gdb.base/help.exp: help
+PASS: gdb.base/help.exp: help thread find

Checked in.

It was not a regression, it is a new test since:
	862811ac870a3f8c35e70319fc0e566c79e4c528


Thanks,
Jan


http://sourceware.org/ml/gdb-cvs/2011-03/msg00078.html

--- src/gdb/testsuite/ChangeLog	2011/03/03 16:57:54	1.2618
+++ src/gdb/testsuite/ChangeLog	2011/03/05 13:15:01	1.2619
@@ -1,3 +1,7 @@
+2011-03-05  Jan Kratochvil  <jan.kratochvil@redhat.com>
+
+	* gdb.base/help.exp (help thread find): Fix one forgotten quote.
+
 2011-03-03  Tom Tromey  <tromey@redhat.com>
 
 	* gdb.hp/gdb.aCC/Makefile.in (Makefile): Remove.
--- src/gdb/testsuite/gdb.base/help.exp	2011/02/23 19:20:39	1.50
+++ src/gdb/testsuite/gdb.base/help.exp	2011/03/05 13:15:02	1.51
@@ -655,7 +655,7 @@
 # test help thread apply
 gdb_test "help thread apply" "Apply a command to a list of threads.*" "help thread apply"
 # test help thread find
-gdb_test "help thread find" "Find threads that match a regular.*" help thread find"
+gdb_test "help thread find" "Find threads that match a regular.*" "help thread find"
 # test help thread name
 gdb_test "help thread name" "Set the current thread's name.*" "help thread name"
 # test help tty


             reply	other threads:[~2011-03-05 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05 13:17 Jan Kratochvil [this message]
2011-03-05 19:55 ` Michael Snyder

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=20110305131701.GA1017@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --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