Good question. There is nothing on stderr and process exits with zero exit
code. It is executed on a working copy. If I put it in a loop sometimes it
will work on 2nd or 3rd time.
On May 23, 2012 6:20 PM, "Konstantin Kolinko" <knst.kolinko_at_gmail.com>
wrote:
> 2012/5/23 Tom DeMay <demay.tom_at_gmail.com>:
> > I'm running svn client 1.7.4 on our build machine (Windows Server 2008
> R2)
> >
> > I'm using Cruise Control running as a service that runs nant to build.
> > during the build I need to execute svn info --xml command.
> >
> > Intermittently the results are truncated. But it seems to happen with
> one of
> > our products that we check out from SVN more than any of our other
> products.
> >
> > I have been unable to reproduce this at will and have been unable to
> > reproduce it at all when running from the command line. However, it does
> > occur very frequently when running from our cruise control service.
> >
> > I've been focusing all my attention on NAnt or Cruise Control as being
> the
> > issue. I've tried various tests to make sure the svn process isn't being
> > killed or terminated unexpectedly. But I see no signs of that happening.
> > I've debugged nant and it clearly shows NAnt waiting for the process to
> > terminate completely and makes sure there is no data left on the stream
> > before closing the stream and and makes sure the process has been fully
> > terminated before moving on.
> >
> > Any suggestions on next steps?
> >
>
> Do you read both stdout and stderr? Nothing is printed to stderr?
>
> It is known issue that XML output can be truncated when an error happens.
> http://subversion.tigris.org/issues/show_bug.cgi?id=2656
>
> Do you execute "svn info" on a working copy path, or on an URL?
>
>
> Best regards,
> Konstantin Kolinko
>
Received on 2012-05-24 00:24:25 CEST