-
Notifications
You must be signed in to change notification settings - Fork 27
Negative complete jobs in qstat output #111
Comments
Is this always the case? Or only occasionally? The code that does this parses how many jobs were submitted from the initial log file, then subtracts the number of running / pending jobs etc. I guess I could easily add a check that this number is ≥ 0 (and make it 0 if not), but it would be better to figure out why it's able to get a negative number.. Phil |
@s-andrews / @FelixKrueger - if one of you could send me the CF submission log for a run where this is happened I'll take a look. I think it must be a case that the number of jobs submitted aren't being counted properly. |
here is one, cheers. |
submission log:
Hmm, strange. I agree that it looks like there were 902 jobs submitted there. So it must be over-counting the queued jobs somehow. Ok, next up - could you do a |
Also - I didn't actually explicitly say this myself, but it works fine for me 😁 That's why I'm asking you guys to do stuff. Two more questions:
Phil |
Are you sure you want this? ^^ |
Ah, no good - everything is fine in |
..spoke to soon, there are a lot of different pipeline runs in this file it would seem...!!! |
I see this:
|
yes sorry, it's not like I have nothing to do... :) |
Ah, I need longer qstat output though. The default trims the full job name, I forgot that. Can you instead do |
Here you go: qstat.txt |
Yay, 75114 lines of xml for me to read through. Such a lucky boy! 🥇 |
The text was updated successfully, but these errors were encountered: