On Thu, 11 Apr 2019 at 10:35, Tom Lane <t...@sss.pgh.pa.us> wrote: > In no particular order, here's what I did:
I was surprised to see nothing mentioned about attempting to roughly sort the test order in each parallel group according to their runtime. Shorter running test coming last should reduce the chances of one process doing its last test when all other processes are already done and sitting idle. Of course, this won't be consistent over all hardware, but maybe it could be done as an average time for each test over the entire buildfarm. > 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. -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
