Re: Timeout in jakarta-tomcat-jk2-native

[Sam Ruby]

Ignacio J. Ortega wrote:

This night was the first try on a native build project at gump :) ( was
that ever  tried in gump before ? ;)

A *long* time ago, before gump was anything like it was today... you can still see some of the output here:

http://oss.software.ibm.com/developerworks/opensource/jakarta/buildlog.html#build_jakarta-tomcat

And it was almost working for apache13, our ant script just worked
well.. ;), it was expecting a binary installation for apache13, and
rubyx seems to have the correct installation done..
But the timeout reached before the end of the task :(..

It would be really nice if we could set the expected timeout for a
project in the gump descriptor, something like <project timeout="130"/>
i.e..
How can i tweak timeout for jakarta-tomcat-jk2-native ?

There currently is no way to tweak timeout on a project by project basis. So far, I have strongly resisted requests by other projects to do this... if we allow each project the option of running for hours, then we will soon get to the point where by the time gump completes, the results are not of much interest to anyone.

Is there any reason why jakarta-tomcat-jk2-native should take more than twenty minutes to compile on a 2 gigahertz machine with a gig of RAM?

- Sam Ruby



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]