From: Carl Love via Gdb-patches <gdb-patches@sourceware.org>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PUSHED] gdb/testsuite: add missing skip_python_tests call in py-doc-reformat.exp
Date: Tue, 07 Jun 2022 09:08:16 -0700 [thread overview]
Message-ID: <e54fd5ef1015007a92933d20681f6051692bebf3.camel@us.ibm.com> (raw)
In-Reply-To: <20220606114055.52878-1-aburgess@redhat.com>
Andrew:
Thanks for the fix!
Carl
On Mon, 2022-06-06 at 12:40 +0100, Andrew Burgess via Gdb-patches
wrote:
> Carl,
>
> Thanks for bringing this to my attention. Sorry for the slow reply,
> I've been away for a couple of days.
>
> The problem was that I had missed a call to skip_python_tests in the
> new test script. Recently, GDB was changed so that it will no longer
> build against Python 2, this means on machines without Python 3 there
> will be no Python support, the 'source' command used in the test will
> then fail.
>
> The correct fix is to check that GDB has Python support at the top of
> the test script, which this commit does.
>
> Thanks,
> Andrew
>
> ---
>
> 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.
> ---
> 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
>
prev parent reply other threads:[~2022-06-07 16:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 10:51 [PATCH 0/2] Improve help test for commands defined in Python Andrew Burgess via Gdb-patches
2022-05-17 10:51 ` [PATCH 1/2] gdb: use gdb::unique_xmalloc_ptr<char> for docs in cmdpy_init Andrew Burgess via Gdb-patches
2022-05-26 17:43 ` Tom Tromey
2022-05-28 10:10 ` Andrew Burgess via Gdb-patches
2022-05-17 10:51 ` [PATCH 2/2] gdb/python: improve formatting of help text for user defined commands Andrew Burgess via Gdb-patches
2022-05-17 12:19 ` Eli Zaretskii via Gdb-patches
2022-05-17 22:41 ` Lancelot SIX via Gdb-patches
2022-05-18 10:19 ` Andrew Burgess via Gdb-patches
2022-05-18 12:09 ` Eli Zaretskii via Gdb-patches
2022-05-26 17:46 ` Tom Tromey
2022-05-28 10:11 ` Andrew Burgess via Gdb-patches
2022-05-31 21:54 ` Carl Love via Gdb-patches
2022-05-31 23:10 ` Carl Love via Gdb-patches
2022-06-03 18:05 ` Carl Love via Gdb-patches
2022-06-06 11:40 ` [PUSHED] gdb/testsuite: add missing skip_python_tests call in py-doc-reformat.exp Andrew Burgess via Gdb-patches
2022-06-07 16:08 ` Carl Love via Gdb-patches [this message]
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=e54fd5ef1015007a92933d20681f6051692bebf3.camel@us.ibm.com \
--to=gdb-patches@sourceware.org \
--cc=aburgess@redhat.com \
--cc=cel@us.ibm.com \
/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