| From: | "Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | "Alexander Lakhin" <exclusion(at)gmail(dot)com>, "Peter Eisentraut" <peter(at)eisentraut(dot)org>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Corey Huinker" <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | "Zsolt Parragi" <zsolt(dot)parragi(at)percona(dot)com>, "Nazir Bilal Yavuz" <byavuz81(at)gmail(dot)com>, "Andres Freund" <andres(at)anarazel(dot)de>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: meson: Make test output much more useful on failure (both in CI and locally) |
| Date: | 2026-05-18 15:26:05 |
| Message-ID: | DILWOM7ARTNF.1GR02CZT6CTT5@jeltef.nl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri Apr 24, 2026 at 7:00 PM CEST, Alexander Lakhin wrote:
> I've noticed another disadvantage of this log processing: [1] shows the
> misc_functions test's failure, but we can't see timing of the test anymore:
> # ok 27 + line 6713 ms
> # ... 210 lines omitted ...
> # ok 223 + reloptions 18169 ms
>
> Previously, a test report for the same failure contained:
> ok 139 + merge 19699 ms
> not ok 140 + misc_functions 18003 ms
> ok 141 + sysviews 7925 ms
I didn't address this in my v6 (yet). Primarily because this isn't
related to the pg_regress changes, but rather to my change that started
using command_ok in these tests to run pg_regress. I'm thinking a bit if
we can make this nicer, one way would be to have command_ok take an
optional argument that allows disabling truncation in places where we
know the output won't be huge.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2026-05-18 15:41:01 | Re: [PATCH] psql: Make ParseVariableDouble reject values above max |
| Previous Message | Matheus Alcantara | 2026-05-18 14:42:52 | Re: postgres_fdw: use_scram_passthrough on user mapping is ignored when also set on server |