From: | Jacob Champion <pchampion(at)vmware(dot)com> |
---|---|
To: | "andrew(at)dunslane(dot)net" <andrew(at)dunslane(dot)net>, "peter(dot)eisentraut(at)enterprisedb(dot)com" <peter(dot)eisentraut(at)enterprisedb(dot)com>, "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de> |
Cc: | "daniel(at)yesql(dot)se" <daniel(at)yesql(dot)se>, "ilmari(at)ilmari(dot)org" <ilmari(at)ilmari(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Readd use of TAP subtests |
Date: | 2022-02-25 16:35:39 |
Message-ID: | 93ecc73227ec7f11a1e68db4c70da856a094fc59.camel@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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]:
> Any output that is not a version, a plan, a test line, a YAML block,
> a diagnostic or a bail out is incorrect. How a harness handles the
> incorrect line is undefined. 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
[1] https://testanything.org/tap-version-13-specification.html
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2022-02-25 16:35:45 | Re: Report checkpoint progress with pg_stat_progress_checkpoint (was: Report checkpoint progress in server logs) |
Previous Message | Magnus Hagander | 2022-02-25 16:28:41 | Re: Add parameter jit_warn_above_fraction |