| << Back to previous view |
|
[QB-1710] Quickbuild times out with no logging information
|
|
| Status: | Open |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 5.0.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Keni Popovski | Assigned To: | Robin Shen |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | 5 hours | Time Spent: | Unknown |
| Original Estimate: | 5 hours | ||
| Environment: | Windows QB build agent, Red Hat test server. | ||
| Description |
|
It has been noticed that a child configuration could timeout, and cause it's parent configuration to remain in a waiting state until it also times out. The step status in the child configuration shows that one of the steps did not complete in time, and has the description of "<step name> | failed | <QB machine>". Specifically, there is no time duration for this step's execution, even though the entire configuration has completed.
Subsequently, the parent configuration looked as though it was processing something, but all of it's children had completed (i.e. passed/failed/timeout). The log file for the child configuration, the parent configuration, and all other configurations under the parent, were empty. This includes the other child configurations that had passed. |
| Comments |
| Comment by Robin Shen [ 12/Jul/13 02:00 AM ] |
| I guess you have "trigger other build" step in parent configuration and have it triggering and waiting for child configurations? I tested this scenario and it works as expected (the parent configuration stops as long as child configuration times out). If not, can you please send me a demo database with reproducing instructions? |
| Comment by Keni Popovski [ 12/Jul/13 02:12 AM ] |
| Yes there is a sequential composition within the parent configuration that kicks off the other configs. This is the first time we have seen it. Will collect more information the next time it occurs. Is there anything specific to be looking for? |
| Comment by Robin Shen [ 13/Jul/13 01:05 AM ] |
| If log files are all empty, it seems to me more like a networking issue. Please check console log of the node running the timed out step of child configuration to see if there are any connection refused/reset/timedout error. |