git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 0/3] Make the Git tests emit TAP format

From
Andreas Ericsson <ae@op5.se>
Date
Jun 15, 2010, 16:42 UTC
Message-ID
<4C17AD93.1020402@op5.se>
In-Reply-To
<AANLkTimxE0mqmitRzlXjSAO6v7IOEg4guUnRlzJUyIF1@mail.gmail.com>
On 06/15/2010 05:17 PM, Ævar Arnfjörð Bjarmason wrote:
Show 46 quoted lines
> On Mon, Jun 14, 2010 at 22:10, Ævar Arnfjörð Bjarmason<avarab@gmail.com>  wrote:
>> On Mon, Jun 14, 2010 at 21:49, Jakub Narebski<jnareb@gmail.com>  wrote:
>>> Ævar Arnfjörð Bjarmason<avarab@gmail.com>  writes:
>>>
>>>> All this series does is slightly adjust the raw text output of our
>>>> tests so that it conforms. to the TAP standard, i.e. instead of this:
>>>>
>>>>     $ ./t0005-signals.sh
>>>>     *   ok 1: sigchain works
>>>>     * passed all 1 test(s)
>>>>
>>>> We get this:
>>>>
>>>>     $ ./t0005-signals.sh
>>>>     ok 1 - sigchain works
>>>>     # passed all 1 test(s)
>>>>     1..1
>>>>
>>>> Changing the output format like this gives us the ability to run the
>>>> Git tests with any TAP tool (like prove(1)) at no extra cost. Every
>>>> other existing way of running the tests continues to work, it's just
>>>> easier for machines to read the output now.
>>
>> I'll re-submit a version of the patch with a better commit message
>> which addresses all of the below.
>>
>>> This doesn't tell us if the result of running test suite with
>>> '--verbose' and/or with '--debug' changes, and if changes how?  Is it
>>> compatibile with TAP format so that TAP parsers understand it?
>>
>> It just changes in that the lines that previously said e.g. "*   ok 1:
>> sigchain works" now say "ok 1 - sigchain works".
>>
>> TAP parsers still understand it, since ignoring unknown garbage is
>> part of the TAP standard.
> 
> Actually it doesn't work for all the tests. The following crops up on
> prove -j 10 ./t[0-9]*.sh :: --verbose:
> 
>      ./t1007-hash-object.sh                             (Wstat: 0
> Tests: 19 Failed: 0)
>        Parse errors: Tests out of sequence.  Found (12) but expected (11)
>                      Tests out of sequence.  Found (13) but expected (12)
>                      Tests out of sequence.  Found (14) but expected (13)
>                      Tests out of sequence.  Found (15) but expected (14)
>                      Tests out of sequence.  Found (16) but expected (15)

Why are you using a plan at all? I absolutely detest using planned tap series, and last I heard was that the majority of TAP-fanatics actually agreed that using a plan to run tests was an extraordinarily lousy idea, since it makes it harder to add tests properly.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
Previous: Ævar Arnfjörð BjarmasonNext: Ævar Arnfjörð Bjarmason
Message 13 of 20 in “Make the Git tests emit TAP format”
  1. 0/3 Make the Git tests emit TAP formatÆvar Arnfjörð Bjarmason, Jun 9, 2010
  2. 1/3 Make test-lib.sh emit valid TAP formatÆvar Arnfjörð Bjarmason, Jun 9, 2010
  3. Jakub NarebskiJun 14, 2010
  4. Ævar Arnfjörð BjarmasonJun 14, 2010
  5. 2/3 Skip tests in a way that makes sense under TAPÆvar Arnfjörð Bjarmason, Jun 9, 2010
  6. 3/3 We use TAP so the Perl test can run without scaffoldingÆvar Arnfjörð Bjarmason, Jun 9, 2010
  7. Jakub NarebskiJun 14, 2010
  8. Ævar Arnfjörð BjarmasonJun 14, 2010
  9. Ævar Arnfjörð BjarmasonJun 14, 2010
  10. Junio C HamanoJun 15, 2010
  11. Ævar Arnfjörð BjarmasonJun 15, 2010
  12. Ævar Arnfjörð BjarmasonJun 15, 2010
  13. Andreas EricssonJun 15, 2010
  14. Ævar Arnfjörð BjarmasonJun 15, 2010
  15. 0/5 TAP support for GitÆvar Arnfjörð Bjarmason, Jun 15, 2010
  16. 1/5 Make test-lib.sh emit valid TAP formatÆvar Arnfjörð Bjarmason, Jun 15, 2010
  17. 2/5 Skip tests in a way that makes sense under TAPÆvar Arnfjörð Bjarmason, Jun 15, 2010
  18. 3/5 We use TAP so the Perl test can run without scaffoldingÆvar Arnfjörð Bjarmason, Jun 15, 2010
  19. 4/5 TAP: Say "pass" rather than "ok" on an empty lineÆvar Arnfjörð Bjarmason, Jun 15, 2010
  20. 5/5 TAP: Make sure there's a newline before "ok" under harnessÆvar Arnfjörð Bjarmason, Jun 15, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.