Mark Phippard wrote:
> news <news@sea.gmane.org> wrote on 03/31/2006 04:43:24 PM:
>
>
>> If I understand you correctly, the same tests were also able to run on
>> 1.3.1 after a few tries. "If" there is a "potential deadlock" issue, it
>> may or may not occur every time the test is run, depending on the nature
>>
>
>
>> of the problem, initial conditions, what else is running..
>>
>> If someone is interested in trying to track it down (or see if they
>> can), it may require running tests over a longer period of time on
>> multiple cpu machines perhaps with vary load. I don't have a multi-cpu
>> or dual-core box at this time, so I can't assist.
>>
>
> I run the tests in VMWare, single processor. I would say I always get
> this error, since 1.3.0. However, if I manually start svnserve prior to
> running the tests, I never get the error.
>
> I do not understand how the test suite works in terms of starting svnserve
> on Windows, but could it have something to do with that? Like is one
> Python thread running svnserve and another the tests but they are in the
> same process and that is triggering some problem?
>
> Wildly speculating.
>
No, win-tests.py uses the win32all extensions and calls CreateProcess to
start svnserve in a new console. The python process is the (ultimate)
parent of both svnserve and svn, but I can't imagine how they would
interact.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 1 00:13:42 2006