check_job_exit_status assumes success when sacct fails or returns empty output

[charparr]

sacct errors or returns no output, check_job_exit_status returns (True, [], 0) with only a warning which to my eye treats "unknown status" as success. I think we'd probably want to do the opposite.