Re: dblib test t002 hanging when run against SQL Server 2008r2 SP2 ?

Frediano Ziglio <[email protected]>
Newsgroups gmane.comp.db.tds.freetds
Message-ID <CAHt6W4c-r3EEvtTZ8=-v9_cJS5xStCkr7cxNV3egPyYCOZLrkw@mail.gmail.com>
2015-06-12 15:40 GMT+01:00 Ramiro Morales <[email protected]>:
> On Fri, Jun 12, 2015 at 10:54 AM, Frediano Ziglio <[email protected]> wrote:
>
>>
>> Looks like you reached the limit, see
>> https://ci.appveyor.com/project/ramiro/freetds/build/174/job/mrcry453g61o351d/messages
>>
>> However the test log show only 16 minutes... (well.. this would
>> possible means that test really hung).
>>
>
> Exactly,  the builds for free AppVeyor open source accounts have a max
> TTL of 40min:
>
> https://ci.appveyor.com/project/ramiro/freetds/build/174
>
> after which I suspect the simply kill the corresponding VM. But the
> process reaches the lockup point way earlier and the rest of the time
> up to min 40 is spent in that frozen state.
>
> I've just restarted the build so I can measure it more precisely but
> 16 mins sounds reasonable.
>
> update: Indeed, the execution reaches the problematic test on minute 14 or 15.
>
> Wil try removing anyways and try to reproduce this here. Thanks!
>
>
> Regards,
>

Oh... after row 46 the test does some on row buffering. However should
print something :(
Output buffering is disabled by

setbuf(stdout, NULL);
setbuf(stderr, NULL);

in common.c. After printing row 46 should enter in dbnextrow and print
it entered there...
I would start adding some printf in t0002.c test. Mostly around line
"verify(46, "...

Frediano
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.