Re: Reducing the runtime of the core regression tests - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Reducing the runtime of the core regression tests
Date
Msg-id 12465.1554957842@sss.pgh.pa.us
Whole thread Raw
In response to Re: Reducing the runtime of the core regression tests  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: Reducing the runtime of the core regression tests
List pgsql-hackers
David Rowley <david.rowley@2ndquadrant.com> writes:
> I was surprised to see nothing mentioned about attempting to roughly
> sort the test order in each parallel group according to their runtime.

I'm confused about what you have in mind here?  I'm pretty sure pg_regress
launches all the scripts in a group at the same time, so that just
rearranging the order they're listed in on the schedule line shouldn't
make any noticeable difference.  If you meant changing the order of
operations within each script, I don't really want to go there.
It'd require careful per-script analysis, and to the extent that the
existing tests have some meaningful ordering (admittedly, many don't),
we'd lose that.

>> Thoughts?  Anyone object to making these sorts of changes
>> post-feature-freeze?

> I think it's a good time to do this sort of thing.  It should be
> easier to differentiate tests destabilising due to this change out
> from the noise of other changes that are going in.... since currently,
> the rate of those other changes should not be very high. Doing it any
> later in the freeze does not seem better since we might discover some
> things that need to be fixed due to this.

Yeah.  I wouldn't propose pushing this in shortly before beta, but
if we do it now then we've probably got a month to sort out any
problems that may appear.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Cleanup/remove/update references to OID column
Next
From: David Rowley
Date:
Subject: Re: Should we add GUCs to allow partition pruning to be disabled?