| << Back to previous view |
|
[QB-3664] Introduce a pulse/ping notion for timeouts
|
|
| Status: | Open |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | Benoit Maury-Bouet | Assigned To: | Robin Shen |
| Resolution: | Unresolved | Votes: | 3 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
Dear all,
It would be nice if we could have another settings for timeouts like this: Don't timeout if process is still sending data (stdout/stderr) Which could also go with a "kill process if still running for XXX" (true timeout in this case) Is it clear ? |
| Comments |
| Comment by Benoit Maury-Bouet [ 10/Feb/21 01:00 PM ] |
|
So to give a little more detail
If I set 30 min timeout on a process that doesn't have this option check, as before step will be timedout if not finished under 30 min If I set 30 min timeout on a process WITH the option enabled, the timeout will only start as soon as no outputs are made, and be resert if you is made, if none are received after 30 min => timeout If I set 30 min timeout on a process WITH the option enabled and a "kill process if still running for" is set for 2h, then even if there was outputs received => timeout after 2h of the job running |
| Comment by Robin Shen [ 10/Feb/21 01:13 PM ] |
| Thanks. This is very clear. |