Closed tfausak closed 1 year ago
@tfausak I've got #68 now to fix this issue. But I've not decided whether both, onJobFailed
and onJobTimeout
, are required or only onJobFailed
is good-enough (with TimeoutException
being treated as just another reason for failure). Any thoughts?
I'd be fine with combining both the "failed" and "timeout" callbacks into one.
The config has a few callbacks for job lifecycle events:
cfgOnJobStart
cfgOnJobSuccess
cfgOnJobFailed
cfgOnJobTimeout
Of those,
cfgOnJobSuccess
andcfgOnJobFailed
appear to be called correctly. As far as I can tell the other two,cfgOnJobStart
andcfgOnJobTimeout
, are never used.cfgOnJobStart
is wired into theonJobStart
method of theHasJobRunner
class forRunnerM
, butonJobStart
itself is never called.cfgOnJobTimeout
appears to be completely unused.