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

Re: svn behavior when the 'post-commit' hook fails

From: Vincent Lefevre <vincent+svn_at_vinc17.org>
Date: Thu, 12 Mar 2009 03:44:21 +0100

On 2009-02-26 11:27:56 -0500, David Weintraub wrote:
> Are you printing anything to STDERR?


> If not, add a few "print STDERR ..." statements to your post-commit
> trigger. Subversion will only output STDERR when the hook fails and
> never outputs STDOUT. When the hook fails, at least you have some
> information as to what is going on with your program.

I don't want to output such messages in general. Only when the hook
fails. But I don't know why it has failed. Perhaps there's a bug in


but then, this needs to be fixed. The problem is that this error
could never be reproduced. And if the hook script died for some
reason (e.g. a signal), only an error message from Subversion
itself can say what happened (e.g. which signal).

> Put at least one line near the beginning of your hook to simply
> announce that you are executing the hook script. That way, you know
> that the hook script actually executed, and it didn't exit before it
> got to a place where it printed something to STDERR.

Well, since I received the e-mail message, this means that the hook
was executed and commit-email.pl even terminated normally (I suppose).

Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
Received on 2009-03-12 03:45:26 CET

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

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