Target that should not run yet fails

[LudvigOlsen]

Target that should not run yet fails

[dansondergaard]

What does jobinfo say about target A? Could it be that A didn't produce that output files it should, but still completed with a zero return code? Then B would start running, but fail since an input file is missing.

Does it still say "submitted" after some time? Slurm is a bit unreliable when it comes to fetching the status, so it can take 10-30 seconds before it reports the correct status for a job/target.

If you can produce a minimal example the reproduces the error, that would be great!

[LudvigOlsen]

It starts running after a short while. A is quite a long job (currently fails after 20+ minutes due to some bugs I'm working through).

Jobinfo for A:

Start times are identical in jobinfo:
B: 2023-05-17T13:58:42 A: 2023-05-17T13:58:42

End time for B is 2023-05-17T13:58:52, A is still running.

Will see if I can make a reproducible example in the coming days :-) (It's 8PM here in Singapore)

[dansondergaard]

Can you provide the complete output of gwf info for target B? Also, can you provide the path (over e-mail) to the workflow file? Thanks :-)

[LudvigOlsen]

I've sent it all in a mail :-)