On 2/25/22 08:39, Peter Eisentraut wrote: > On 24.02.22 16:00, Andres Freund wrote: >> I've incidentally played with subtests yesterdays, when porting >> src/interfaces/libpq/test/regress.pl to a tap test. Unfortunately it >> seems >> that subtests aren't actually specified in the tap format, and that >> different >> libraries generate different output formats. The reason this matters >> somewhat >> is that meson's testrunner can parse tap and give nicer progress / error >> reports. But since subtests aren't in the spec it can't currently parse >> them... > > Ok that's good to know. What exactly happens when it tries to parse > them? Does it not count them or does it fail somehow? The way the > output is structured > > t/001_basic.pl .. > # Subtest: vacuumlo --help > ok 1 - exit code 0 > ok 2 - goes to stdout > ok 3 - nothing to stderr > 1..3 > ok 1 - vacuumlo --help > > it appears that it should be able to parse it nonetheless and should > just count the non-indented lines.
AIUI TAP consumers are supposed to ignore lines they don't understand. The Node TAP setup produces output like this, so perl is hardly alone here. See <https://node-tap.org/docs/api/subtests/> cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com