Re: Need a builtin way to run all tests faster manner
Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
From: ilmari@ilmari.org (Dagfinn Ilmari Mannsåker )
To: Simon Riggs <simon@2ndquadrant.com>
Cc: 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-07T13:09:29Z
Lists: pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes: > On 7 March 2017 at 20:36, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > >> FWIW, +1 on improving matters here. > > +1 also. > > I don't see what's wrong with relying on buildfarm though; testing is > exactly what its there for. > > If we had a two-stage process, where committers can issue "trial > commits" as a way of seeing if the build farm likes things. If they > do, we can push to the main repo. In perl we do this by having the smoke testers (build farm) pick up branches with a specific prefix (smoke-me/ in our case, typically smoke-me/<username>/<topic>), in addition to the blead (master) and maint-x.y (release) branches. -- "I use RMS as a guide in the same way that a boat captain would use a lighthouse. It's good to know where it is, but you generally don't want to find yourself in the same spot." - Tollef Fog Heen
Commits
-
Improve isolation tests infrastructure.
- 60f826c5e624 10.0 landed