From: ludo@gnu.org (Ludovic Courtès)
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: PEG Parser
Date: Sat, 22 Jan 2011 22:02:16 +0100 [thread overview]
Message-ID: <87aaisr6sn.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTikPStAEGy0bJQ7QwdDhCie4DsnXJArAxEhuqEFT@mail.gmail.com> (Noah Lavine's message of "Fri, 21 Jan 2011 10:23:00 -0500")
Hello!
Noah Lavine <noah.b.lavine@gmail.com> writes:
>> “./check-guile --coverage peg.test” can be used to measure code
>> coverage, normally.
>
> I tried running that, but what all I got was this output:
>
> Running peg.test
>
> Totals for this test run:
> passes: 21
> failures: 0
> unexpected passes: 0
> expected failures: 0
> unresolved test cases: 0
> untested test cases: 0
> unsupported test cases: 0
> errors: 0
>
> That seems incorrect, but I don't know anything about check-guile.
It should have produced $top_builddir/guile.info, which can be used as
input to LCOV to generate an HTML code coverage report
(http://ltp.sourceforge.net/coverage/lcov.php).
Thanks,
Ludo’.
next prev parent reply other threads:[~2011-01-22 21:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 21:29 PEG Parser Noah Lavine
2011-01-17 21:32 ` Ludovic Courtès
2011-01-21 15:23 ` Noah Lavine
2011-01-22 21:02 ` Ludovic Courtès [this message]
2011-01-24 1:29 ` Noah Lavine
2011-01-24 20:55 ` Ludovic Courtès
2011-01-27 1:40 ` Noah Lavine
2011-01-27 2:23 ` Michael Lucy
2011-01-27 2:38 ` Noah Lavine
2011-01-27 3:02 ` Michael Lucy
2011-01-27 5:17 ` Noah Lavine
2011-01-28 3:25 ` Noah Lavine
2011-01-28 5:13 ` Michael Lucy
2011-01-28 15:48 ` Andy Wingo
2011-01-29 3:07 ` Noah Lavine
2011-01-29 4:15 ` Michael Lucy
2011-01-29 11:34 ` Andy Wingo
2011-01-29 19:37 ` Noah Lavine
2011-01-30 11:43 ` Andy Wingo
2011-02-02 0:26 ` Noah Lavine
2011-02-06 15:31 ` Noah Lavine
2011-02-18 22:03 ` Andy Wingo
2011-02-23 15:10 ` Noah Lavine
2011-03-04 10:52 ` Andy Wingo
2011-03-04 13:09 ` Noah Lavine
2011-01-29 11:33 ` Andy Wingo
-- strict thread matches above, loose matches on Subject: below --
2010-05-27 5:19 Michael Lucy
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aaisr6sn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).