On Mon, Jan 17, 2022 at 12:16:19PM -0800, Andres Freund wrote: > I think it might still be worth adding stopgap way of running all tap tests on > windows though. Having a vcregress.pl function to find all directories with t/ > and run the tests there, shouldn't be a lot of code...
I started doing that, however it makes CI/windows even slower. I think it'll be necessary to run prove with all the tap tests to parallelize them, rather than looping around directories, many of which have only a single file, and are run serially. https://github.com/justinpryzby/postgres/commits/citest-cirrus This has the link to a recent cirrus result if you'd want to look. I suppose I should start a new thread. There's a bunch of other stuff for cirrus in there (and bits and pieces of other branches). . cirrus: spell ccache_maxsize . cirrus: avoid unnecessary double star ** . vcregress/ci: test modules/contrib with NO_INSTALLCHECK=1 . vcregress: style . wip: vcsregress: add alltaptests . wip: run upgrade tests with data-checksums . pg_regress --initdb-opts . wip: pg_upgrade: show list of files copied only in vebose mode . wip: cirrus: include hints how to install OS packages.. . wip: cirrus: code coverage . cirrus: upload html docs as artifacts . wip: cirrus/windows: save compiled build as an artifact
