[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Failing svnrdump_tests.py#43 with 1.7.x on Windows (was: Re: 1.7.3 next week-ish?)

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Thu, 9 Feb 2012 20:50:04 +0100

On Thu, Feb 9, 2012 at 7:59 PM, Greg Stein <gstein_at_gmail.com> wrote:
>
> On Feb 9, 2012 1:23 PM, "Paul Burba" <ptburba_at_gmail.com> wrote:
>>
>> On Thu, Feb 9, 2012 at 11:49 AM, Daniel Shahaf <danielsh_at_elego.de> wrote:
>> >...
>
>> > It is suggested there that setting
>> > libsvn_ra_serf/update.c:MAX_NR_OF_CONNS
>> > to "2" will prevent ra_serf from driving multiple window handlers
>> > concurrently and thus avoid the bug.  (Presumably by causing the file to
>> > finish on the right side of the errant close_directory() call.)
>>
>> I just tried MAX_NR_OF_CONNS=2 with
>> ^/subversion/branches/1.7.x_at_1242422 and the test still fails:
>
> Woah. Weird. I may have been mistaken. Please try 1.
>
> If that fails, then more investigation is needed.

I just tried with MAX_NR_OF_CONNS=1 and it still fails.

This is the client-side where I need to adjust this setting, right?
The last failure I've seen was with a trunk_at_1242116+MAX_NR_OF_CONNS=1
client vs. 1.7.x_at_1239697 mod_dav_svn (r1239697 is the backport that
started breaking things).

-- 
Johan
Received on 2012-02-09 20:50:56 CET

This is an archived mail posted to the Subversion Dev mailing list.