| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jim Nasby <jim(dot)nasby(at)openscg(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Need a builtin way to run all tests faster manner |
| Date: | 2017-03-11 00:06:27 |
| Message-ID: | f101a252-9faa-466e-2586-5e708ca04671@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/10/17 19:00, Jim Nasby wrote:
> 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.
Those people who know what they're doing will presumably run all those
checks before they submit a patch. It's those people who send in
patches that don't apply cleanly or fail the tests that would benefit
from this system. But if they're that careless, then they also won't
take care to use this particular system correctly.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-03-11 00:13:25 | Re: WIP: Faster Expression Processing v4 |
| Previous Message | Peter Eisentraut | 2017-03-11 00:04:39 | Re: Need a builtin way to run all tests faster manner |