On 9/7/07, Kamesh Jayachandran <kamesh@collab.net> wrote:
> Hi,
>
> Since r26476 I observed SIGABRT over ra_dav due to uncleared
> error(--enable-maintainer-mode build), This commit seems to fix it.
> Though I could not understand the fix or no mention of the same.
>
> Refer merge_tests.py's
> 'avoid_repeated_merge_using_inherited_merge_info'. Commit of r5 was
> causing this SIGABRT.
>
> I could see the 'uncleared error to be' "File not found: transaction
> '4-4', path '/A/B/E/alpha'".
>
> In r26489 and pre-26476 this error does not happen.
>
> Dav http request level difference between r26476 and r26489 is 'CHECKOUT
> /svn-test-work/repositories/merge_tests-1/!svn/ver/1/A/B/E/alpha'
>
> r26476 makes this 'CHECKOUT' req and gets the error which is not handled
> and left uncleared.
>
> Pre r26476 and r26489 does not make this extra CHECKOUT request and
> hence no SIGABRT.
>
> I could see in general this commit to be 're-org' type of commit except
> few functional bits like 'remove_wcprops', though I could not connect
> this changes to 'removal of one extra CHECKOUT'.
>
> Can someone explain here?
Yes. This is due to the existance of the wcprops between r26476 and
26489, because since r26476 - even though it looks like the contrary -
we failed to remove the wcprops.
HTH,
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 7 13:07:28 2007