
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 12/Jul/13 12:18 AM
Updated: 13/Jul/13 01:05 AM
|
|
Component/s: |
None
|
Affects Version/s: |
5.0.7
|
Fix Version/s: |
None
|
|
Original Estimate:
|
5 hours
|
Remaining Estimate:
|
5 hours
|
Time Spent:
|
Unknown
|
Environment:
|
Windows QB build agent, Red Hat test server.
|
|
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.
|
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.
|
Show » |
|