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

Re: svn commit: r1422706 - in /subversion/trunk/subversion: libsvn_subr/opt.c tests/cmdline/svntest/main.py

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 18 Dec 2012 10:11:48 +0100

On Tue, Dec 18, 2012 at 09:54:08AM +0100, Stefan Sperling wrote:
> I've seen this happen in Jenkins builds that run 'svn export' and
> adding --non-interactive fixed it.

Correction: I misrembered. This wasn't happening in Jenkins, but in an
automated test environment ("SQS Test") which executes batch scripts on
remote Windows boxes without giving users an interactive shell.

But really, any program that runs 'svn' and collects stdout/stderr data
to generate a report based on that is affected by this problem, if it
waits until the 'svn' process is done before process collected data.
The controlling process cannot tell whether 'svn' is taking a long
time to produce another line on stdout, or whether 'svn' hangs.
Received on 2012-12-18 10:12:32 CET

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