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

Re: [PATCH] Re: All breakage tests failing in svn_io_file_rename

From: <jszakmeister_at_comcast.net>
Date: 2003-11-12 21:40:01 CET

> Or, if is it a real error? Here is the actual log for that test:
>
> CMD: svn "export" "--username" "jrandom" "--password" "rayjandom"
> "svn://localhost/repositories/export_tests-6"
> "working_copies/export_tests-6.export" "--config-dir"
> "/data/svntest/obj-st/subversion/tests/clients/cmdline/local_tmp/config"
> <TIME = 0.056166>
> =============================================================
> Expected mu and actual mu are different!
> =============================================================
> EXPECTED NODE TO BE:
> =============================================================
> * Node name: mu
> Path: __SVN_ROOT_NODE/A/mu
> Contents: This is the file 'mu'.$LastChangedRevision: 2 $ $LastChangedBy:
> jrandom $
> Properties: {}
> Attributes: {}
> Children: is a file.
> =============================================================
> ACTUAL NODE FOUND:
> =============================================================
> * Node name: mu
> Path: A/mu
> Contents: This is the file 'mu'.$LastChangedRevision: 2 $ $LastChangedBy:
> $

This makes me think that the test repository isn't doing authentication of any sort (hence, the author field being empty). Does anyone know how the breakage machines are set up for testing? I assumed when writing the export test for keyword translation that we had some sort of authentication in place so that we could properly test all the keywords. Perhaps I was wrong in making that assumption?

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 12 21:53:21 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.