Re: Re: [farm-report] Failed to build python-SunOS-5.8-sun4d-fafner

Anders Qvist <[email protected]> writes:

> On Tue, Jul 23, 2002 at 09:39:24AM +0200, Per Cederqvist wrote:
> >
> > A new test run should never be started before the previous test run
> > has finished.  You could send a warning if a test run doesn't finish
> > when expected.
> 
> This is a known problem. Something in the tests bogs down on sunos
> 5.8 (at least on proton and fafner).
> 
> I try to keep these from doing too much harm by ulimit, but I have not
> found a viable way of deciding when the build script has executed long
> enough. Any suggestions would be very welcome. buildit.sh, line 146:
> 
>   (make $target 9>&1 1>&2 2>&9 | tee $makeerrlog) > $makelog 2>&1

Do you use "ulimit -t" to set the maximum CPU time?  However, that
would not have helped in this case, since the processes used very
little CPU.  They seemd to be stuck waiting for something.

> When some predetermined time has passed, if still on this line,
> all children should be killed.
> 
> Hmm. Maybe I should just put a stamp file somewhere, to check for
> before we start building targets in a particular module. If that file
> is still present at next execution, we report that build got stuck?

Yes, that would be better, and allow the computers to continue with
other tasks even when you do not babysit it.  :-)

Killing the processes makes it hard to find out what was wrong.  If
you allow them to continue to run, and report an "already running"
error to the list, somebody can attach a debugger or strace to the
hung process and see what it is doing.

        /ceder