public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] [gdb/testsuite] Skip language auto in gdb.base/parse_number.exp
Date: Mon, 23 May 2022 06:55:50 +0000 (GMT)	[thread overview]
Message-ID: <20220523065550.22F22383E6A8@sourceware.org> (raw)

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

commit cb0d58bf4d274cfb1ae11b75bd2b3ba81c8d371d
Author: Tom de Vries <tdevries@suse.de>
Date:   Mon May 23 08:55:46 2022 +0200

    [gdb/testsuite] Skip language auto in gdb.base/parse_number.exp
    
    In test-case gdb.base/parse_number.exp, we skip architecture auto in the
    $supported_archs loop, to prevent duplicate testing.
    
    Likewise, skip language auto and its alias local in the $::all_languages
    loop.  This reduces the number of tests from 17744 to 15572.
    
    Tested on x86_64-linux, with a build with --enable-targets=all.

Diff:
---
 gdb/testsuite/gdb.base/parse_number.exp | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/gdb/testsuite/gdb.base/parse_number.exp b/gdb/testsuite/gdb.base/parse_number.exp
index 444f5d0534b..197e27a8e9e 100644
--- a/gdb/testsuite/gdb.base/parse_number.exp
+++ b/gdb/testsuite/gdb.base/parse_number.exp
@@ -63,6 +63,10 @@ proc test_parse_numbers {arch} {
 
     foreach_with_prefix lang $::all_languages {
 	if { $lang == "unknown" } {
+	    # Tested outside $supported_archs loop.
+	    continue
+	} elseif { $lang == "auto" || $lang == "local" } {
+	    # Avoid duplicate testing.
 	    continue
 	}
 
@@ -117,6 +121,7 @@ set all_languages [get_set_option_choices "set language"]
 
 foreach_with_prefix arch $supported_archs {
     if {$arch == "auto"} {
+	# Avoid duplicate testing.
 	continue
     }
     test_parse_numbers $arch


                 reply	other threads:[~2022-05-23  6:55 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=20220523065550.22F22383E6A8@sourceware.org \
    --to=vries@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).