Buildforge Step timeout
![]()
In our new BF 8.0 installation - The build step is continually seeing step time out errors at 5 minutes. Step setting has been changed to other values, including zero, which should prevent the TMO.
263 7/11/13 8:04 PM TMO Timeout after 300 seconds. * This is with the step timeout setup to 60 minutes and the build output piped to a log file. |
2 answers
![]()
This sounds like a defect that was fixed in the 7.1.1.2-ish timeframe (in the perl engine). The agent heartbeats were not being processed properly by the engine. We worked around that by ensuring that output was being produced (the defect was only seen in "quiet" steps that produced little or no output).
A script that forks the command to be run as a background process, then waits for it to finish while dumping a timestamp every minute, seemed to fix the problem.
If the fix from the other thread works for you too Dennis, it would be simpler to implement.
This should be reported as a defect.
|
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Hi - am running into the same issue but was able to overcome with another workaround, see the thread
https://jazz.net/forum/questions/53019/timeout-in-minutes-from-project-step
But still want to see if some one from BF team can help answer the timing out after 5 mins issue , though we configure the step timeout greater than 5 mins . Is this a bug in BF 8.0? I have the same step in 7.1.x and its working fine there