Re: pg_regress: schedule multi-line test groups

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Alexandre Felipe <o(dot)alexandre(dot)felipe(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Daniel Gustafsson <daniel(at)yesql(dot)se>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: pg_regress: schedule multi-line test groups
Date: 2026-11-16 19:46:18
Message-ID: CAN4CZFM7pY6JOOMZzu3KJ1RSZbRBJbC=JsAXseWr6uR_kg2kLg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 15 Nov 2026, Alexandre Felipe <o(dot)alexandre(dot)felipe(at)gmail(dot)com> wrote:
> Yes, intentionally, the patch preamble mentions that.

ops, I missed that, sorry.

1. Now with 2.3:

$ cat s
test: a
test: b
$ pg_regress ... --schedule=s --max-concurrent-tests=0
# in schedule file "s" line 1, test a: max concurrency (0) exceeded
Bail out!

While --help still says that 0 means unlimited. (and
--max-concurrent-tests=abc is also 0, but that's a different issue)

2. long commented out lines can run tests

test:
a
# xxxx...(1019 x)...xxxx b

"All 2 tests passed"

+/*
+ * Maximum supported number of concurrent tests
+ */
+#define MAX_PARALLEL_TESTS 100

This is now defined twice.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Jones 2026-11-16 20:06:46 Re: ISBN range table
Previous Message Zsolt Parragi 2026-11-16 19:36:32 Re: [PATCH] Preserve replication origin OIDs in pg_upgrade