try changing this line
{ sleep 5; kill $$; } &
to
{ sleep 30; kill $$; } &
if it goes away then its a test timing issue
looking at those particular tests it won't hurt the working cases/machines
to change the timeout to 30 -- they will finish sooner and terminate
the watcher process way before the timeout
On Wed, 1 Aug 2012 02:14:09 +0200 Roland Mainz wrote:
> On Tue, Jul 31, 2012 at 11:34 PM, Glenn Fowler <g...@research.att.com> wrote:
> > there hasn't been much chatter about the 2012-07-27 beta
> > we're hoping to make it official on friday
> > so please bang on the beta so we have a chance at a stable release
> > thanks
> We're getting sporadic failures in "coprocess.sh on Solaris
> 11/32bit/optimised builds:
> -- snip --
> test coprocess(en_US.UTF-8) begins at 2012-08-01+02:09:25
> coprocess.sh[236]: /bin/cat coprocess 2 hung
> test coprocess(en_US.UTF-8) failed at 2012-08-01+02:09:53 with exit
> code 1 [ 35 tests 1 error ]
> test coprocess(shcomp) begins at 2012-08-01+02:09:53
> shcomp-coprocess.ksh[236]: /bin/cat coprocess 2 hung
> -- snip --
> Note the machine had other stuff (working on "poll" builtin) at the
> same time... it may this was just a plain timeout because the machine
> was loaded to heavily...
> ----
> Bye,
> Roland
> --
> __ . . __
> (o.\ \/ /.o) roland.ma...@nrubsig.org
> \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
> /O /==\ O\ TEL +49 641 3992797
> (;O/ \/ \O;)
_______________________________________________
ast-developers mailing list
ast-developers@research.att.com
https://mailman.research.att.com/mailman/listinfo/ast-developers
