Al Chu
well, job status is: `PENDING, RUNNING, COMPLETED, FAILED, or CANCELED` COMPLETED, FAILED, or CANCELED are just replacements for INACTIVE given what happened with a job. Perhaps we can just axe...
> I think this is what we're arguing for. For INACTIVE jobs we can split out into COMPLETED, FAILED, CANCELED and TIMEOUT since that is useful. It just turned out...
> Such problems might include Also symlink infinite loops. i.e. errno = ELOOP > Since all operations in a transaction look like (key, treeobj) tuples, I guess the limitation on...
but can't a symlink "reference" something? and therefore something in the KVS should be preserved vs garbage collected?
re-pushed fixing the nit that @grondo noted above. removed WIP, will set MWP
re-pushed, rebasing on PR #4070 and fixing up some conflicts due to #4278 changes
just rebasing on #4070
rebased on master, since it'd been awhile
> Also, in the end, it would be nice if sysadmins could configure any supported resource control property for jobs when the sdexec implementation is being used. However, looking at...
re-pushed with fixes per comments above, went ahead and squashed since they were pretty minor changes