It's all about the answers!

Ask a question

Buildforge Step timeout

dennis cook (124) | asked Jul 01 '13, 5:52 p.m.
edited Jul 12 '13, 1:40 p.m.
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.

Vinod Reddy commented Aug 07 '13, 12:12 p.m.

Hi  - am running into the same issue but was able to overcome with another workaround, see the thread

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

2 answers

permanent link
Robert haig (1.0k16) | answered Aug 07 '13, 4:38 p.m.
This sounds like a defect that was fixed in the 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.

permanent link
dennis cook (124) | answered Apr 17 '14, 2:24 p.m.
This has been fixed in BF

Your answer

Register or to post your answer.