Re: Readd use of TAP subtests - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Readd use of TAP subtests
Date
Msg-id ef9faaa4b9938f4e1f58d581c96f02e21aaac67d.camel@vmware.com
Whole thread Raw
In response to Re: Readd use of TAP subtests  (Jacob Champion <pchampion@vmware.com>)
List pgsql-hackers
On Fri, 2022-02-25 at 16:35 +0000, Jacob Champion wrote:
> On Fri, 2022-02-25 at 09:43 -0500, Andrew Dunstan wrote:
> > AIUI TAP consumers are supposed to ignore lines they don't understand.
> 
> It's undefined behavior [1]:

And of course the minute I send this I notice that I've linked the v13
spec instead of the original... sorry. Assuming Perl isn't marking its
tests as version 13, you are correct:

> Any output line that is not a version, a plan, a test line, a
> diagnostic or a bail out is considered an “unknown” line. A TAP
> parser is required to not consider an unknown line as an error but
> may optionally choose to capture said line and hand it to the test
> harness, which may have custom behavior attached. This is to allow
> for forward compatability. Test::Harness silently ignores incorrect
> lines, but will become more stringent in the future. TAP::Harness
> reports TAP syntax errors at the end of a test run.

--Jacob

pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Report checkpoint progress with pg_stat_progress_checkpoint (was: Report checkpoint progress in server logs)
Next
From: Magnus Hagander
Date:
Subject: Re: Expose JIT counters/timing in pg_stat_statements