Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i75W3-0002D8-RO for pgsql-hackers@arkaria.postgresql.org; Sun, 08 Sep 2019 22:18:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i75W1-0001R5-W1 for pgsql-hackers@arkaria.postgresql.org; Sun, 08 Sep 2019 22:18:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i75W1-0001Q5-Ga for pgsql-hackers@lists.postgresql.org; Sun, 08 Sep 2019 22:18:37 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1i75Vy-0002M0-R2 for pgsql-hackers@lists.postgresql.org; Sun, 08 Sep 2019 22:18:36 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x88MIXAM018364; Sun, 8 Sep 2019 18:18:33 -0400 From: Tom Lane To: Andrew Dunstan cc: pgsql-hackers@lists.postgresql.org Subject: Re: MSVC buildfarm critters are not running modules' TAP tests In-reply-to: <688d32cf-19be-c8f0-f08b-fde25d15132e@2ndQuadrant.com> References: <6628.1567958876@sss.pgh.pa.us> <5e1113b9-e1a6-d68b-c05c-06e607a4cd5f@2ndQuadrant.com> <17551.1567979940@sss.pgh.pa.us> <688d32cf-19be-c8f0-f08b-fde25d15132e@2ndQuadrant.com> Comments: In-reply-to Andrew Dunstan message dated "Sun, 08 Sep 2019 18:14:52 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <18362.1567981113.1@sss.pgh.pa.us> Date: Sun, 08 Sep 2019 18:18:33 -0400 Message-ID: <18363.1567981113@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andrew Dunstan writes: > On 9/8/19 5:59 PM, Tom Lane wrote: >> Hm. Changing the buildfarm script would be an alternative way to >> fix the issue so far as the buildfarm is concerned, but it doesn't >> seem like it provides any useful way for one to manually invoke >> the tests on Windows. Or am I missing something about how that's >> usually done? > The invocation is: > vcregress.pl taptest [ PROVE_FLAGS=xxx ] directory Sure, I saw that you can run one test that way ... but what do you do when you want the equivalent of check-world? (I'm surprised that vcregress hasn't already got a "world" option. But at least there should be a determinate list of what you need to run to get all the tests.) regards, tom lane