On Wed, Oct 6, 2021 at 6:53 AM Alvaro Herrera <alvhe...@alvh.no-ip.org> wrote: > > On 2021-Oct-06, Michael Paquier wrote: > > > On Tue, Oct 05, 2021 at 06:18:47PM -0400, Andrew Dunstan wrote: > > > On 10/5/21 4:38 PM, Andres Freund wrote: > > >> My problem with that is that that means there's no convenient way to > > >> discover > > >> what one needs to do to run all tests. Perhaps we could have one > > >> all-taptest > > >> target or such? > > > > > > Yeah. That's a much better proposal. > > So how about "vcregress check-world"?
I was thinking of the same. +1 for "vcregress check-world" which is more in sync with it's peer "make check-world" instead of "vcregress all-taptest". I'm not sure whether we can also have "vcregress installcheck-world" as well. Having said that, with these new options, are we going to have only below? vcregress check vcregress installcheck vcregress check-world vcregress installcheck-world (?) And remove others? vcregress plcheck vcregress contribcheck vcregress modulescheck vcregress ecpgcheck vcregress isolationcheck vcregress bincheck vcregress recoverycheck vcregress upgradecheck Regards, Bharath Rupireddy.
