On 3/16/21 4:09 PM, David Malcolm wrote:
[updating subject for greater visibility]

On Tue, 2021-03-16 at 08:51 -0600, Martin Sebor wrote:
On 3/16/21 3:08 AM, Martin Liška wrote:
On 3/15/21 9:57 PM, Martin Sebor wrote:
Any plans to integrate it into the testsuite?  (That way we presu
mably
wouldn't need to remember to run it by hand.)

Likely not, I'm not so big friend with DejaGNU.
Are you willing to help me with that?

I'm not a fan either but that's what we've got.  And sure, I'll help
if/when I can.  I think it should be "straightforward" to rewrite
the script in Expect (as much as anything is straightforward in
Expect).  Or, it could stay as is and be invoked from some .exp
file in testsuite.  Although is Python a required prerequisite
for running the testsuite?  If not, it might be better to either
rewrite the script in something that is (e.g., AWK) or in Expect.

I find it painful writing non-trivial logic in Tcl.

Me too!


We already have run-gcov-pytest in gcov.exp which calls out to a
python3 script, checking if python3 is supported, and bailing with
UNSUPPORTED otherwise.

FWIW I think it's reasonable to have something similar for this case.

Yep, let's run the existing Python script.

Martin


Dave


Reply via email to