Repository navigation
incoda v0.10.0
incoda v0.10.0 - run limits that free a wedged job's slot
run takes two limits, per call or as a lane default through config:
--max-run DURkills the job once it has held the lane that long (exit 131)--stall DURkills the job when its process tree has used no CPU for that long (exit 132)
--stall calibrates before it arms: a hidden spin must move the CPU counter within 6 s, or the limit disarms with a warning naming the platform, so a dead counter can never kill a busy job. The kill and release lines record which limit fired.
Lane defaults stamp config schema 3 while any limit is set; binaries older than v0.7.0 refuse such a lane with exit 122 instead of running it unbounded.
Platform notes: the darwin CPU counter is not proven, so --stall warns and disarms there; linux runs the stall counter through CI only. On Windows a job that exits 0 is never reported as limited; on Unix a max-run kill landing inside the child's exit window can report 131 for a job that finished, a known residual (#35).