Horton

Re: Need a builtin way to run all tests faster manner

Jim Nasby <jim.nasby@openscg.com>

View thread View on postgr.es
From: Jim Nasby <jim.nasby@openscg.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Magnus Hagander <magnus@hagander.net>, Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, Stephen Frost <sfrost@snowman.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2017-03-11T00:00:31Z
Lists: pgsql-hackers 
On 3/10/17 5:57 PM, Peter Eisentraut wrote:
> On 3/10/17 14:53, Jim Nasby wrote:
>> The biggest win we'd get from something like Travis would be if the
>> commitfest monitored for new patch files coming in for monitored threads
>> and it created a new branch, applied the patches, and if they applied
>> without error commit the branch and push to let Travis do it's thing. We
>> wouldn't want that running in the main git repo, but it should be fine
>> in a fork that's dedicated to that purpose.
>
> This has been discussed several times before, e.g.,
>
> https://www.postgresql.org/message-id/54DD2413.8030201@gmx.net

Maybe instead of having the commitfest app try and divine patches from 
the list it should be able to send patches to the list from a specified 
git repo/branch. Anyone that provides that info would have tests run 
automagically, patches sent, etc. Anyone who doesn't can just keep using 
the old process.
-- 
Jim Nasby, Chief Data Architect, OpenSCG
http://OpenSCG.com

Commits

  1. Improve isolation tests infrastructure.