Arwin,

Sorry, I guess my description can be reduced to even simple form.

I mean we do not need *failed commit* condition, just scheduled change alone is enough.

Can you provide a new patch which covers the following case?

cd /tmp
cd svn-1.6 co file:///repo/abc
touch abc/test
svn-1.6 add abc/test
svn-1.7 upgrade


With regards
Kamesh Jayachandran
On 12/31/2010 02:58 PM, Arwin Arni wrote:
On Thursday 30 December 2010 09:35 PM, Kamesh Jayachandran wrote:
Hi All,

I did the following.

cd /tmp
cd svn-1.6 co file:///repo/abc
touch abc/test
svn-1.6 add abc/test
#Make sure below commit fails either by a pre-commit hook or File system perm error, we just need this to fail.

svn-1.6 ci -m "msg"

svn-1.7 upgrade
Segfaults

My svn-1.7 trunk build corresponds to 1053813:1053833

With regards
Kamesh Jayachandran
Hi Kamesh,

I've written an XFail test case which reproduces this Seg Fault in upgrade_tests.py

I've attached the patch + log message and also a .tar.bz2 file to be added to
subversion/tests/cmdline/upgrade_tests_data/

Regards,
Arwin Arni


Reply via email to