On Thu, 2022-02-24 at 08:46 -0800, Andres Freund wrote: > One annoying bit is that our current tap invocation infrastructure for msvc > won't know how to deal with that. We put the build directory containing t/ > onto PATH, but that won't work for test/. But we also don't want to install > test binaries. Not sure what the solution for that is.
Would it help if the C executable, not Perl, was the thing actually producing the TAP output? The binaries built from test/ could be placed into t/. Or does that just open up a new set of problems? --Jacob
