On Sun, 15 Nov 2026, Alexandre Felipe <[email protected]> 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.


Reply via email to