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

[Firebird-devel] Test bugs.core_3554 randomly fails

2016-06-17 Thread Dimitry Sibiryakov
Hello, all. 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, used in subj test query