From: Jeff Law <law@redhat.com>
To: "Martin Liška" <mliska@suse.cz>,
"David Malcolm" <dmalcolm@redhat.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Add pytest for a GCOV test-case
Date: Tue, 5 Jan 2021 16:36:24 -0700 [thread overview]
Message-ID: <9021ed74-22d4-5f2a-c60f-4e0bc63e48b6@redhat.com> (raw)
In-Reply-To: <ef9f6c9f-df2f-2a77-0f35-22c30bd92c7d@suse.cz>
On 12/23/20 6:03 AM, Martin Liška wrote:
> At a high level, this patch calls out to Python 3, allowing for test
>> logic to be written in Python, rather than Tcl. Are we doing this
>> anywhere else in our test suite?
>
> No.
I'm surprised. I thought we did this for some of David's work at some
point. Clearly I'm mis-remembering.
>>
>> The test implicitly requires python3, and the 3rd party pytest module
>> installed within it. What happens if these aren't installed? (ideally
>> an UNSUPPORTED at the DejaGnu level, I think).
>
> Right now, one will see the following in the .log file:
>
> /usr/bin/python3: No module named pytest
>
>
> I must confess that I don't know how to properly mark that as UNRESOLVED
> in DejaGNU.
I think it's just something like
unresolved "could not find python interpreter $testcase" in
run-gcov-pytest if you find the right magic in the output of your spawn.
Jeff
next prev parent reply other threads:[~2021-01-05 23:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 11:39 Martin Liška
2020-12-22 17:49 ` David Malcolm
2020-12-23 13:03 ` Martin Liška
2021-01-05 23:36 ` Jeff Law [this message]
2021-01-07 16:14 ` Martin Liška
2021-01-08 20:29 ` Jeff Law
2021-01-13 13:38 ` Rainer Orth
2021-01-13 14:08 ` David Malcolm
2021-01-13 14:30 ` Rainer Orth
2021-01-14 8:56 ` Martin Liška
2021-01-14 13:22 ` Rainer Orth
2021-01-14 13:27 ` Rainer Orth
2021-01-14 13:33 ` Martin Liška
2021-01-15 12:28 ` Rainer Orth
2021-01-15 13:48 ` Martin Liška
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=9021ed74-22d4-5f2a-c60f-4e0bc63e48b6@redhat.com \
--to=law@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).