public inbox for [email protected]  
help / color / mirror / Atom feed
From: Jelte Fennema-Nio <[email protected]>
To: Alexander Lakhin <[email protected]>
To: Peter Eisentraut <[email protected]>
To: Andrew Dunstan <[email protected]>
To: Corey Huinker <[email protected]>
Cc: Zsolt Parragi <[email protected]>
Cc: Nazir Bilal Yavuz <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: meson: Make test output much more useful on failure (both in CI and locally)
Date: Mon, 18 May 2026 17:26:05 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<luhx26gz3tiqkndldbobukt4zeaeu2ppd5qgsibf6hknhq6d7e@kngeuarhk5dg>
	<[email protected]>
	<CAN55FZ3w-3z=js-3We78P41heKCY1aOMsUz3p7UrQa7amGWL7g@mail.gmail.com>
	<[email protected]>
	<CAN4CZFMOBeKh51LqxjMGSSYHWTGPXAE33e+ZWnGgFKm21LJpfw@mail.gmail.com>
	<[email protected]>
	<CADkLM=dr-e_k7sh5PL36Hn7G5z6Xno1XHCwAQurv5UWSaUq4-g@mail.gmail.com>
	<[email protected]>
	<CADkLM=d51SaMF+w+k33EhGAFOeP0VQdUZS1mE__dJKkanm2jkw@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>

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.






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: meson: Make test output much more useful on failure (both in CI and locally)
  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