A satellite needs a project-specific timeout, so that builds that take far too long are terminated. There have been taskwarrior commits where the unit tests just hang. Consequently this hangs the satellite. A timeout would let the satellite recover and continue.
A timeout value should be included in build.msg request. Note that this timeout would have to be long enough to accommodate the slowest platform/machine, so it would need to be something like 30 minutes for taskwarrior.
Currently the only workaround to this is to stop and restart the satellites.
pbeckingham
commented
6 years ago
A satellite needs a project-specific timeout, so that builds that take far too long are terminated. There have been taskwarrior commits where the unit tests just hang. Consequently this hangs the satellite. A timeout would let the satellite recover and continue.
A timeout value should be included in build.msg request. Note that this timeout would have to be long enough to accommodate the slowest platform/machine, so it would need to be something like 30 minutes for taskwarrior.
Currently the only workaround to this is to stop and restart the satellites.