public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Daniel Gustafsson <[email protected]>
Cc: vignesh C <[email protected]>
Cc: Nikolay Shaplov <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Dagfinn Ilmari Mannsåker <[email protected]>
Cc: PostgreSQL Developers <[email protected]>
Cc: Andrew Dunstan <[email protected]>
Cc: Tom Lane <[email protected]>
Subject: Re: TAP output format in pg_regress
Date: Wed, 29 Mar 2023 09:08:05 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<5348601.u5redSiXY4@thinkpad-pgpro>
<[email protected]>
<CALDaNm0k6iOhzwxCi16B9gHCVpHUsh_AM85ugX4KJdMTTxq8xg@mail.gmail.com>
<CALDaNm0WtGHpU5iZNfd8nDJ-avEw+btFNJvv7qVOPLy6BZG=dw@mail.gmail.com>
<CALDaNm21roPooMrok6u6jxPciWyeLGen9qBnavD67=gJdswNrw@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On 28.03.23 15:56, Daniel Gustafsson wrote:
>> On 28 Mar 2023, at 15:26, Daniel Gustafsson <[email protected]> wrote:
>
>> I think the attached is a good candidate for going in, but I would like to see it
>> for another spin in the CF bot first.
>
> Another candidate due to a thinko which raised a compiler warning.
This is incorrect:
-echo "+++ tap install-check in $(subdir) +++" && \
+echo "\# +++ tap install-check in $(subdir) +++" && \
It actually prints the backslash.
But this appears to be correct:
pg_regress_check = \
- echo "+++ regress check in $(subdir) +++" && \
+ echo "\# +++ regress check in $(subdir) +++" && \
(Maybe because it's in a variable definition?)
I'm confused why all the messages at the end lost their period ("All
tests passed", "A copy of the test summary ...", etc.). As long as they
are written as sentences, they should have a period.
There is a comment "Testnames are indented 8 spaces" but you made that
into a macro now, which is currently defined to 3.
There is an unexplained #if 0.
The additions of
+ free(difffilename);
+ difffilename = NULL;
+ free(logfilename);
+ logfilename = NULL;
in the success case are not clear. The program is going to end soon anyway.
On the indentation of the test names: If you look at the output of
meson test verbose mode (e.g., meson test -C _build --suite regress
--verbose), it reproduces the indentation in a weirdly backwards way, e.g.,
▶ 1/1 stats 981 ms OK
▶ 1/1 event_trigger 122 ms OK
▶ 1/1 oidjoins 172 ms OK
▶ 1/1 fast_default 137 ms OK
▶ 1/1 tablespace 285 ms OK
Not sure by which logic it arrives at that, but you can clearly see 3
additional spaces for the single tests.
One thing I have noticed while playing around with this is that it's
quite hard to tell casually whether a test run has failed or is failing,
if you just keep half an eye on it in another Window. The display of
"ok"/"not ok" as well as the summaries at the end are much less
prominent than the previous "ok"/"FAILED" and the summary box at the
end. I'm not sure what to do about that, or if it's just something to
get used to.
view thread (14+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: TAP output format in pg_regress
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox