Re: meson and check-tests

Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>

From: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>

To: Nazir Bilal Yavuz <byavuz81@gmail.com>

Cc: jian he <jian.universality@gmail.com>, Tristan Partin <tristan@partin.io>, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-07-18T07:19:53Z

Lists: pgsql-hackers

Attachments

0002-Expand-test-selection-behavior-to-all-test--20250718.patch (text/x-patch) patch 0002
0001-Add-make-check-tests-behavior-to-the-meson--20250718.patch (text/x-patch) patch 0001

Hi All,

On Mon, Jan 27, 2025 at 11:22 AM Ashutosh Bapat
<ashutosh.bapat.oss@gmail.com> wrote:
>
> On Mon, Nov 25, 2024 at 7:06 PM Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
> >
> > It is added and marked as ready for the committer [1]. There are
> > multiple 'Jian He' users in the commitfest app, so I couldn't add you
> > as a reviewer; please add yourself.
> >
> > [1] https://commitfest.postgresql.org/51/5405/
>
> In order to debug a failure in SQL/PGQ patch, I needed to run
> regression test with some instrumentation which caused the regression
> run to take more than 1000 seconds. The failure is seen only in one of
> the tests. Spending 1000 seconds to reproduce or test patch just for
> one test seems too expensive. If we commit this patch, we could
> instead run check-tests equivalent in meson to save time and
> resources. The patch is ready for a committer already.

The patches still apply and the CF is in RFC state. Reattaching them
to get some attention.

-- 
Best Wishes,
Ashutosh Bapat