Re: [Firebird-devel] test

2019-02-18 Thread Mark Rotteveel
On 17-2-2019 18:36, liviuslivius wrote: test message, because i have send two emails 16.02.2019 23:12 and 16.02.2019 23:27 but i still do see them on the group I have them in my mailbox now, it looks like they were stuck for almost a day within SourceForge: Received: from [127.0.0.1] (helo=

Re: [Firebird-devel] Test - please ignore

2017-09-30 Thread Vlad Khorsun via Firebird-devel
Test 2 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/li

Re: [Firebird-devel] Test bugs.core_3554 randomly fails

2016-06-18 Thread Alex Peshkoff
On 06/17/2016 07:11 PM, Dimitry Sibiryakov wrote: > 17.06.2016 17:58, Dmitry Yemanov wrote: >> Or perhaps do such a check in the remote client, or even better in the >> Y-valve? > In this case the test will fail always. > > Tests are also fixed sometimes ;) --

Re: [Firebird-devel] Test bugs.core_3554 randomly fails

2016-06-17 Thread Dimitry Sibiryakov
17.06.2016 17:58, Dmitry Yemanov wrote: > Or perhaps do such a check in the remote client, or even better in the > Y-valve? In this case the test will fail always. -- WBR, SD. -- What NetFlow Analyzer can do for

Re: [Firebird-devel] Test bugs.core_3554 randomly fails

2016-06-17 Thread Dmitry Yemanov
17.06.2016 17:13, Dimitry Sibiryakov wrote: > > As most of you know, when routine protocol.cpp:alloc_cstring() receives zero > length, it > behaves differently, depending on previous allocations. In some cases it > returns pointer > to zero-length string, in some - NULL pointer. > Because of this