On Tue, Nov 6, 2012 at 10:53 AM, Stefan Fuhrmann
<stefan.fuhrm...@wandisco.com> wrote:
> On Mon, Nov 5, 2012 at 2:00 AM, Johan Corveleyn <jcor...@gmail.com> wrote:
>>
>> Before I look into this further, I'd like to know if anyone else has seen
>> this or can reproduce this (or doesn't reproduce this with a similar
>> environment) ...
>>
>> Tests 12 and 15 of mergeinfo-test.exe and test 4 of skel-test.exe hang on
>> my machine (i.e. they don't do anything useful anymore, but do fully consume
>> a cpu core until I kill them).
>>
>> This is with trunk@1405553. All other tests, except the above three, run
>> successfully for me. I'm running Windows XP (32 bit).
>>
>> I only see this happening with a release build (shared; haven't tried with
>> --disable-shared yet), when compiled with VS 2010.
>>
>> I do *not* see this (i.e. tests complete normally) with:
>> - debug build made with VS 2010.
>> - release or debug builds made with VSExpress 2008.
>>
>> Does anyone else have a release build on (any) Windows, made with VS 2010,
>> and can run these tests?
>>
>> I'm using these dependencies:
>> Httpd 2.2.22
>> Apr 1.4.5
>> Apr-Util 1.4.1
>> Apr-Iconv 1.2.1
>> OpenSSL 1.0.1c
>> Serf 1.1.1
>> SQLite 3.7.14.1
>> ZLib 1.2.6
>
>
> They don't hang for me but I'm using a slightly older SQLite version.
> However, there has been a similar issue under Linux when running
> the tests in parallel. Python 2.7.2(?) has a sync. issue. Maybe, try
> updating your python installation.
Thanks a lot for taking a look, Stefan.
I have tried again with SQLite 3.7.12, but the result is the same. You
did use VC2010 for compilation, and tried with a release build, right?
Which SQLite version did you use actually?
I'm not running the test suite in parallel, and I'm also seeing it
when I run only that single test:
python win-tests.py -c --release -t mergeinfo-test.exe#12 R:\test
Besides I'm using Python 2.7.3, which IIUC is the latest production
release of the 2.x family.
Thanks for the suggestion though.
I guess the next step for me is to try and reproduce this when running
from within the IDE ... or try bisecting.
> But I did run across an assertion in mergeinfo.c, :line 1174
> during merge_tests.py 125:
>
> SVN_ERR_ASSERT_NO_RETURN(IS_VALID_FORWARD_RANGE(first));
>
Hm, I haven't seen that one yet (I'm looking specifically at
merginfo-test.exe, not merge_tests.py, but I did run the rest of the
test suite successfully, so this has definitely passed for me --
though as I said, I don't run them in parallel).
--
Johan
