public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb/testsuite: add missing skip_python_tests call in py-doc-reformat.exp
Date: Mon,  6 Jun 2022 11:40:42 +0000 (GMT)	[thread overview]
Message-ID: <20220606114042.7849C3858C74@sourceware.org> (raw)

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

commit 772f4c2e98100e2bc3277bb7a214b8751c1cf968
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Mon Jun 6 12:16:56 2022 +0100

    gdb/testsuite: add missing skip_python_tests call in py-doc-reformat.exp
    
    In commit:
    
      commit 51e8dbe1fbe7d8955589703140ca5eba7b4f1bd7
      Date:   Mon May 16 19:26:54 2022 +0100
    
          gdb/python: improve formatting of help text for user defined commands
    
    the test that was added (gdb.python/py-doc-reformat.exp) was missing a
    call to skip_python_tests.  As a result, this test would fail for any
    GDB built within Python support.
    
    This commit adds a call to skip_python_tests.

Diff:
---
 gdb/testsuite/gdb.python/py-doc-reformat.exp | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/gdb/testsuite/gdb.python/py-doc-reformat.exp b/gdb/testsuite/gdb.python/py-doc-reformat.exp
index aae3939bd07..f0cfa278557 100644
--- a/gdb/testsuite/gdb.python/py-doc-reformat.exp
+++ b/gdb/testsuite/gdb.python/py-doc-reformat.exp
@@ -19,6 +19,10 @@
 
 load_lib gdb-python.exp
 
+# Check that Python is supported.
+clean_restart
+if { [skip_python_tests] } { continue }
+
 # A global counter used to number the tests.
 set idx 0


                 reply	other threads:[~2022-06-06 11:40 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=20220606114042.7849C3858C74@sourceware.org \
    --to=aburgess@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).