On Thu, Sep 17, 2026 at 9:03 AM Michael Paquier <[email protected]> wrote:
> On Thu, Sep 17, 2026 at 08:57:51AM +0100, Alexandre Felipe wrote: > > This was motivated by two rebases on the SLOPE patch [1] this week due to > > changes in parallel_schedule. Also I find much easier to parse the list > > using this syntax, if we stick with one test per line we get the benefit > of > > counting tests by looking at the line numbers. > > > > I used a `goto` to keep the number of touched lines small, and facilitate > > your review. I'd +1 something like that in the schedule files, even if we only > limit the number of tests per line to be up to 20. > Actually, I think we should support arbitrary size test groups and run them on a pool from a queue that would possibly make the regression faster as today we always wait for the slowest test in each group. > +test: > + boolean > + char > + name > > At least, let's make the whitespace vs tab policy consistent. ;) > I will blame the editor, I hit tab and it adds spaces :) I started manually but then I saw that what I was doing was dumb and error prone, and did the rest with find and replace (with \t) now all using spaces. Regards, Alexandre
v1.1-0001-pg_regress-multi-line-test-groups.patch
Description: Binary data
