[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PEG Parser
From: |
Ludovic Courtès |
Subject: |
Re: PEG Parser |
Date: |
Sat, 22 Jan 2011 22:02:16 +0100 |
User-agent: |
Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux) |
Hello!
Noah Lavine <address@hidden> 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’.
- PEG Parser, Noah Lavine, 2011/01/13
- Re: PEG Parser, Ludovic Courtès, 2011/01/17
- Re: PEG Parser, Noah Lavine, 2011/01/21
- Re: PEG Parser,
Ludovic Courtès <=
- Re: PEG Parser, Noah Lavine, 2011/01/23
- Re: PEG Parser, Ludovic Courtès, 2011/01/24
- Re: PEG Parser, Noah Lavine, 2011/01/26
- Re: PEG Parser, Michael Lucy, 2011/01/26
- Re: PEG Parser, Noah Lavine, 2011/01/26
- Re: PEG Parser, Michael Lucy, 2011/01/26
- Re: PEG Parser, Noah Lavine, 2011/01/27
- Re: PEG Parser, Noah Lavine, 2011/01/28
- Re: PEG Parser, Michael Lucy, 2011/01/28
- Re: PEG Parser, Andy Wingo, 2011/01/28