Closed gdevenyi closed 8 years ago
Good catch. Let's write a test for this and then a fix. :-)
I agree a warning here makes sense... perhaps only under verbose mode?
Test is hard since Travis doesn't have a real qstat...
Yes, warn on verbose makes sense
Test is hard since Travis doesn't have a real qstat...
Yeah, either factor out the call to qstat so that there is a testable function that only inspects the output, or mock the call to subprocess or mock qstat (kinda cool actually).
Overkill?
Overkill for now.
Fixed by #86
If qstat -x returns nothing, ET parsing fails, triggering an exception and breaking qbatch.
qbatch stops at this point, but it should probably check for qstat -x having no output or at least warn that no dependencies are possible because of no jobs running.