Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Tests for the target description XML parser
Date: Fri, 09 Mar 2007 00:05:00 -0000	[thread overview]
Message-ID: <200703090004.l2904o9W002368@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070308232029.GA17914@caradoc.them.org> from "Daniel Jacobowitz" at Mar 08, 2007 06:20:29 PM

Daniel Jacobowitz wrote:

> Nope.  You should probably detect that and skip the remaining tests in
> that file.

Like so?

Bye,
Ulrich



ChangeLog:

	* gdb.xml/tdesc-arch.exp: Test is unsupported on target with
	just a single architecture.

Index: gdb/testsuite/gdb.xml/tdesc-arch.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.xml/tdesc-arch.exp,v
retrieving revision 1.2
diff -u -p -r1.2 tdesc-arch.exp
--- gdb/testsuite/gdb.xml/tdesc-arch.exp	8 Feb 2007 21:14:12 -0000	1.2
+++ gdb/testsuite/gdb.xml/tdesc-arch.exp	9 Mar 2007 00:01:17 -0000
@@ -32,6 +32,11 @@ gdb_test_multiple "set architecture" $ms
 	set arch2 $expect_out(2,string)
 	pass $msg
     }
+    -re "Requires an argument. Valid arguments are (\[^ \]*), auto\\.\r\n$gdb_prompt $" {
+	# If there is just one supported architecture, we can't do this test.
+	unsupported "tdesc-arch.exp"
+	return -1
+    }
 }
 
 set default_arch ""


-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2007-03-09  0:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 17:14 Daniel Jacobowitz
2007-03-08 23:10 ` Ulrich Weigand
2007-03-08 23:20   ` Daniel Jacobowitz
2007-03-09  0:05     ` Ulrich Weigand [this message]
2007-03-09  0:10       ` Daniel Jacobowitz
2007-03-09  0:14         ` Ulrich Weigand

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=200703090004.l2904o9W002368@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=drow@false.org \
    --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