Key: |
QB-2013
|
Type: |
Bug
|
Status: |
Open
|
Priority: |
Major
|
Assignee: |
Robin Shen
|
Reporter: |
AlSt
|
Votes: |
0
|
Watchers: |
1
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 08/Apr/14 09:27 AM
Updated: 16/May/14 12:34 AM
|
|
Component/s: |
None
|
Affects Version/s: |
5.1.18
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
File Attachments:
|
None
|
Image Attachments:
|
|
|
On some nodes the step status and the live log is not up-to-date during a build. In the screenshots you can see that the build is already running a couple of minutes and no live log (also no log from master step) in which the build seems to "hang" (but does not really, it only shows it is still in master step, but the build runs as it should).
|
Description
|
On some nodes the step status and the live log is not up-to-date during a build. In the screenshots you can see that the build is already running a couple of minutes and no live log (also no log from master step) in which the build seems to "hang" (but does not really, it only shows it is still in master step, but the build runs as it should). |
Show » |
|
1. Screenshot of the non-stopping build as you've shown me right now
2. Stack trace of both QB server and involved agent.
3. Memory dump of both QB server and involved agent.
4. Build log of the non-stopping build
5. System log of both QB server and involved agent (resides under <QB server/agent install dir>/logs). In case the system log is not being flushed quickly, you may need to change property "log4j.logger.com.pmease.quickbuild" to "WARN" in file "conf/log4j.properties".
Please take all these info while this issue is happening, so that I can associate timing with memory/threads for that particular instance of issue. Please zip and upload the memory dump to our ftp server.