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: Fri, 8 Jan 2021 13:29:06 -0700 [thread overview]
Message-ID: <22518cff-7efb-ea90-0b16-6ad88c3d9970@redhat.com> (raw)
In-Reply-To: <d813c44a-e157-3da7-21f2-c678e9aaecc1@suse.cz>
On 1/7/21 9:14 AM, Martin Liška wrote:
> On 1/6/21 12:36 AM, Jeff Law wrote:
>> unresolved "could not find python interpreter $testcase" in
>> run-gcov-pytest if you find the right magic in the output of your spawn.
>
> Achieved that with the updated patch.
>
> Ready for master?
> Thanks,
> Martin
>
> 0001-Add-pytest-for-a-GCOV-test-case.patch
>
> From 53f5169156044acf8ecec498aa89d6be44c7173a Mon Sep 17 00:00:00 2001
> From: Martin Liska <mliska@suse.cz>
> Date: Mon, 21 Dec 2020 09:14:28 +0100
> Subject: [PATCH] Add pytest for a GCOV test-case
>
> gcc/testsuite/ChangeLog:
>
> PR gcov-profile/98273
> * lib/gcov.exp: Add run-gcov-pytest function which runs pytest.
> * g++.dg/gcov/pr98273.C: New test.
> * g++.dg/gcov/gcov.py: New test.
> * g++.dg/gcov/test-pr98273.py: New test.
OK
jeff
next prev parent reply other threads:[~2021-01-08 20:29 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
2021-01-07 16:14 ` Martin Liška
2021-01-08 20:29 ` Jeff Law [this message]
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=22518cff-7efb-ea90-0b16-6ad88c3d9970@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).