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] Add skip_python_tests in gdb.python/tui-window-names.exp
Date: Mon, 24 Oct 2022 06:36:46 +0000 (GMT)	[thread overview]
Message-ID: <20221024063646.982143858439@sourceware.org> (raw)

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

commit b347f578952a29ff9b02090b0dafec563520c80b
Author: Tom de Vries <tdevries@suse.de>
Date:   Mon Oct 24 08:36:42 2022 +0200

    [gdb/testsuite] Add skip_python_tests in gdb.python/tui-window-names.exp
    
    I did a gdb build without python support, and during testing ran into FAILs in
    test-case gdb.python/tui-window-names.exp.
    
    Fix this by adding the missing skip_python_test.
    
    Tested on x86_64-linux.

Diff:
---
 gdb/testsuite/gdb.python/tui-window-names.exp | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/gdb/testsuite/gdb.python/tui-window-names.exp b/gdb/testsuite/gdb.python/tui-window-names.exp
index 8aaf3b42229..ff7dab5bd15 100644
--- a/gdb/testsuite/gdb.python/tui-window-names.exp
+++ b/gdb/testsuite/gdb.python/tui-window-names.exp
@@ -26,6 +26,11 @@ if {[skip_tui_tests]} {
     return
 }
 
+if { [skip_python_tests] } {
+    untested "skipping Python tests"
+    return
+}
+
 # Define a function we can use as a window constructor.  If this ever
 # gets called we'll throw an error, but that's OK, this test doesn't
 # actually try to create any windows.

                 reply	other threads:[~2022-10-24  6: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=20221024063646.982143858439@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).