Re: PATH manipulation in 001_libpq_pipeline.pl fails on windows
От | Andrew Dunstan |
---|---|
Тема | Re: PATH manipulation in 001_libpq_pipeline.pl fails on windows |
Дата | |
Msg-id | 87875257-f359-4480-a709-88c58b7497c5@dunslane.net обсуждение исходный текст |
Ответ на | PATH manipulation in 001_libpq_pipeline.pl fails on windows (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: PATH manipulation in 001_libpq_pipeline.pl fails on windows
|
Список | pgsql-hackers |
On 9/30/21 5:40 PM, Andres Freund wrote: > Hi, > > For me 001_libpq_pipeline.pl doesn't reliably work on windows, because it > tries to add something to PATH, using unix syntax (vs ; used on windows). > > $ENV{PATH} = "$ENV{TESTDIR}:$ENV{PATH}"; > > If the first two elements in PATH are something needed, this can cause the > test to fail... I'm surprised this doesn't cause problems on the buildfarm - a > plain > perl src\tools\msvc\vcregress.pl taptest src\test\modules\libpq_pipeline\ > fails for me. Not sure. That's certainly an error. But why are we mangling the PATH at all? Wouldn't it be better just to call command_ok with "$ENV{TESTDIR}/libpg_pipeline" ? cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: