Joshua Zahner
Joshua Zahner
Im pretty sure I fixed this. It was a bug in sbatch_conditional.bash where I wasn't properly handling providing full file paths for those two job files.
I'm still testing. Will push tonight.
This was originally a line met for debugging purposes, but I have retained so I can verify if anything wacky occurs. A job very briefly has no state associated with...
I've actually known about this for a while. It's something to do with how the script terminates and how that termination handle buffer flushing. It might not be easily fixable.
Regarding `logging improvement`: What constitutes "waiting" status type? Regarding `Support multiple queues`: is the `$QUEUE` variable always set? Can I just use that to lookup the limit from `qlimits`? Regarding...
Re `logging improvement`: That text string will only start printing after all of the jobs associated with a task have been submitted, so there will never be any "WAITING" jobs...
That last comment didn't tell me anything. Is this scenario fine? Since those log lines won't appear until everything has been submitted, I don't see a point in leaving a...
Correction concerning `logging improvement`: jobs could enter the WAITING state after initial job submission if jobs fail and need are resubmitted. I don't print the table in that case, and...
> * **Overview over all running jobs** > It would be great to have a function`job_status` that shows what is running and where they are. This may require a `~/.minsar`...