public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Simon Marchi <simark@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb/testsuite: fix xfail in gdb.ada/ptype_tagged_param.exp
Date: Tue, 31 Jan 2023 16:36:04 +0000 (GMT)	[thread overview]
Message-ID: <20230131163604.6AA433858D28@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d8e88d10d8687d61ddb09fc0a0af563c43071555

commit d8e88d10d8687d61ddb09fc0a0af563c43071555
Author: Simon Marchi <simon.marchi@efficios.com>
Date:   Tue Jan 31 11:34:38 2023 -0500

    gdb/testsuite: fix xfail in gdb.ada/ptype_tagged_param.exp
    
    I see:
    
        ERROR: wrong # args: should be "xfail message"
            while executing
        "xfail "no debug info" $gdb_test_name"
            ("uplevel" body line 3)
            invoked from within
        "uplevel {
                if {!$has_runtime_debug_info} {
                    xfail "no debug info" $gdb_test_name
                } else {
                    fail $gdb_test_name
                }
            }"
    
    This is because the xfail takes only one argument, fix that.
    
    Change-Id: I2e304d4fd3aa61067c04b5dac2be2ed34dab3190

Diff:
---
 gdb/testsuite/gdb.ada/ptype_tagged_param.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.ada/ptype_tagged_param.exp b/gdb/testsuite/gdb.ada/ptype_tagged_param.exp
index da9b2bb3ae6..ba21e7b8e3c 100644
--- a/gdb/testsuite/gdb.ada/ptype_tagged_param.exp
+++ b/gdb/testsuite/gdb.ada/ptype_tagged_param.exp
@@ -49,7 +49,7 @@ gdb_test_multiple "ptype s" "ptype s" {
     }
     -re -wrap $nodebug {
 	if {!$has_runtime_debug_info} {
-	    xfail "no debug info" $gdb_test_name
+	    xfail "$gdb_test_name (no debug info)"
 	} else {
 	    fail $gdb_test_name
 	}

                 reply	other threads:[~2023-01-31 16:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230131163604.6AA433858D28@sourceware.org \
    --to=simark@sourceware.org \
    --cc=gdb-cvs@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).