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

Re: svn rev 4704: FAIL (ra_svn, sparc-sun-solaris2.8 static)

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2003-02-02 19:24:48 CET

On Sun, Feb 02, 2003 at 03:00:53PM -0500, dev@subversion.tigris.org wrote:
> Running all tests in prop_tests.py...FAILURE
> At least one test FAILED, checking /export/paulsboro1/mprice/private/src/test-svn/tests.log
> FAIL: prop_tests.py 11: set and get a revprop change
> CMD: svnadmin "create" "repositories/prop_tests-11"
> CMD: svnadmin dump "local_tmp/repos" | svnadmin load "repositories/prop_tests-11"
> CMD: svn "co" "--username" "jrandom" "--password" "rayjandom" "svn://localhost/repositories/prop_tests-11" "working_copies/prop_tests-11"
> CMD: svn "propset" "--revprop" "-r" "0" "cash-sound" "cha-ching!" "working_copies/prop_tests-11"
> svn: A repository hook failed.
> svn: pre-revprop-change hook failed with error output:
>
> FAIL: prop_tests.py 11: set and get a revprop change
> END: prop_tests.py
>

Okay, I've trimmed the uninteresting parts. The reason this failed is that
subversion requires you to have a pre-revprop-change hook or else it won't
allow you to change rev-props. This is because otherwise you could lose data.

I'm not sure how the tests normally get around this.

Anyone else?

BTW: It would be nice if the From: header on these messages kept your name,
but the Reply-To: Header had dev@subversion.tigris.org.

Thanks for setting this up though!!!

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  • application/pgp-signature attachment: stored
Received on Mon Feb 3 02:27:34 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.