Re: TAP test started using meson, can get a tcp port already used by another test.

2025-02-22 Thread Zharkov Roman
On 2025-02-22 04:11, Andrew Dunstan wrote: On 2025-02-21 Fr 11:49 AM, Andres Freund wrote: Pushed. Thanks Thank you very much! Best regards, Roman Zharkov

Re: TAP test started using meson, can get a tcp port already used by another test.

2025-02-21 Thread Andrew Dunstan
On 2025-02-21 Fr 11:49 AM, Andres Freund wrote: Hi, On 2025-02-21 11:04:49 -0500, Andrew Dunstan wrote: On 2025-02-21 Fr 10:50 AM, Andres Freund wrote: Can we explicitly set the MESON_BUILD_ROOT environment variable when running a test? With included patch for the src/tools/testwrap file, ea

Re: TAP test started using meson, can get a tcp port already used by another test.

2025-02-21 Thread Andres Freund
Hi, On 2025-02-21 11:04:49 -0500, Andrew Dunstan wrote: > On 2025-02-21 Fr 10:50 AM, Andres Freund wrote: > > > Can we explicitly set the MESON_BUILD_ROOT environment variable when > > > running > > > a test? With included patch for the src/tools/testwrap file, each instance > > > gets an unique

Re: TAP test started using meson, can get a tcp port already used by another test.

2025-02-21 Thread Andrew Dunstan
On 2025-02-21 Fr 10:50 AM, Andres Freund wrote: Can we explicitly set the MESON_BUILD_ROOT environment variable when running a test? With included patch for the src/tools/testwrap file, each instance gets an unique TCP port. I don't like that, feels like a "namespace violation" to set a MES

Re: TAP test started using meson, can get a tcp port already used by another test.

2025-02-21 Thread Andres Freund
Hi, On 2025-02-21 15:58:45 +0700, Zharkov Roman wrote: > We running TAP tests which operates with a lot of instances. And some of > these tests randomly fail due "address already in use". It turned out that > the meson does not set environment variable MESON_BUILD_ROOT when running > the test() fu

Re: TAP test started using meson, can get a tcp port already used by another test.

2025-02-21 Thread Andrew Dunstan
On 2025-02-21 Fr 3:58 AM, Zharkov Roman wrote: Hello, We running TAP tests which operates with a lot of instances. And some of these tests randomly fail due "address already in use". It turned out that the meson does not set environment variable MESON_BUILD_ROOT when running the test() func

Re: TAP test started using meson, can get a tcp port already used by another test.

2025-02-21 Thread Zharkov Roman
On 2025-02-21 16:32, Andrew Dunstan wrote: In the meantime you can do what the buildfarm client does and explicitly set PG_TEST_PORT_DIR. Thank you for the answer! We tried to set PG_TEST_PORT_DIR using the 'env' option and it works fine. Best regards, Roman Zharkov

TAP test started using meson, can get a tcp port already used by another test.

2025-02-21 Thread Zharkov Roman
Hello, We running TAP tests which operates with a lot of instances. And some of these tests randomly fail due "address already in use". It turned out that the meson does not set environment variable MESON_BUILD_ROOT when running the test() function [0]. As a result each test uses its own "por