Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
From: <eric.berg@barclayscapital.com>
To: <users@subversion.apache.org>
Date: Wed, 5 Jan 2011 11:30:23 -0500
Subject: Hooks That Use Perl Test::Builder Having Problems with STDERR
Thread-Topic: Hooks That Use Perl Test::Builder Having Problems with STDERR
Thread-Index: Acus9dmkDYKYjl88RM69O2ZpDMQX3w==
Message-ID: 
 <B0011508DF5C184ABEC7A8978D7AB5E80BBC81E678@NYKPCMMGMB03.INTRANET.BARCAPINT.COM>
Accept-Language: en-US, en-GB
Content-Language: en-US
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I'm working on porting a fairly extensive set of CVS hooks to SVN.  The i=
ssue that I'm having now is that my pre-commit hook, which runs a Perl sc=
ript that performs tests based on Test::Builder and Test::More, never sho=
w their stderr on the console.  I see it in the svn web server logs, but =
not on the console.

Has anyone had any experience with a problem like this?  Essentially, the=
=20Test::* modules remap stderr and stdout for the purpose of trapping th=
at output to evaluate it for the tests.  Seems like I have dueling file h=
andles.

Still looking into this; I know I don't have a complete understanding of =
this issue.

Any thoughts on what I might be able to do here?

Eric

_______________________________________________

This e-mail may contain information that is confidential, privileged or o=
therwise protected from disclosure. If you are not an intended recipient =
of this e-mail, do not duplicate or redistribute it by any means. Please =
delete it and any attachments and notify the sender that you have receive=
d it in error. Unless specifically indicated, this e-mail is not an offer=
=20to buy or sell or a solicitation to buy or sell any securities, invest=
ment products or other financial product or service, an official confirma=
tion of any transaction, or an official statement of Barclays. Any views =
or opinions presented are solely those of the author and do not necessari=
ly represent those of Barclays. This e-mail is subject to terms available=
=20at the following link: www.barcap.com/emaildisclaimer. By messaging wi=
th Barclays you consent to the foregoing.  Barclays Capital is the invest=
ment banking division of Barclays Bank PLC, a company registered in Engla=
nd (number 1026167) with its registered office at 1 Churchill Place, Lond=
on, E14 5HP.  This email may relate to or be sent from other members of t=
he Barclays Group.
_______________________________________________