| << Back to previous view |
|
[QB-1358] Impossible to kill some hanging builds in QuickBuild
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Siim Käba | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
From previous response from you (Pmease):
"QB relies on Java's process facility (process.destroy()) to terminate a forked process and it does so by sending SIGTERM. If the process won't respond to this signal, the process is not able to be killed. Sending SIGKILL requires native code on different platforms. Please submit an improvement request at track.pmease.com for this improvement." This would be the request to make it. Cheers! |
| Comments |
| Comment by Robin Shen [ 27/Dec/12 12:25 PM ] |
| If on Windows, this should have been fixed by calling taskkill in QuickBuild. |