[ http://issues.apache.org/jira/browse/GUMP-131?page=comments#action_66176
]
Adam Jack commented on GUMP-131:
--------------------------------
I see this in the code:
TIMEOUT=60*60 # 60 minutes (in seconds)
if os.environ.has_key('GUMP_TIMEOUT'):
TIMEOUT = string.atoi(os.environ['GUMP_TIMEOUT'])
Setting to 0 will (I believe) remove it. The JIRA entry still stands though,
it needs documentation & the error message ought explain it. Personal I
think we need per project configurable timeouts, not server wide. I'll add
that to the JIRA entry sometime.
> Build fails with "build timed out"
> ----------------------------------
>
> Key: GUMP-131
> URL: http://issues.apache.org/jira/browse/GUMP-131
> Project: Gump
> Type: Bug
> Components: Python-based Gump
> Environment: Solaris v2.8, Gump SVN trunk (Python 2.4.1)
> Reporter: Graham Leggett
>
> While compiling a "make" on a very large (compile time 2 hours or more) C/C++
> project, the build is reported as failed with the reason "build timed out".
> The build log shows that the build has been stopped half way through the
> build. There is no obvious evidence that the build has hung in any way.
> If an attempt is made to cd to the build directory and type "make", the build
> completes normally.
> There is no obvious timeout setting that can change this - if there is can
> the "build timed out" message be replaced with a message that says "build
> timed out - increase option ZZZ and try again".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
