hello,
at the moment I am writing scripts that submit jobs to deadline with dependencies.
The problem is that deadline does not respect the order of dependencies.
For example I have a chain of 4 jobs that needs to start one by one.
But once the first one is finished the 3 others start all together.
This makes automated pipeline steps impossible with deadline 6.
can this be fixed ?
How are you specifying the dependencies in your 4 job example? If you have the last three jobs each specify the first job as a dependency, then what you are seeing is normal operation. To do what you want, you’ll have to make the 2nd job dependent on the 1st, the 3rd on the 2nd, and the 4th on the third.
Cheers,
hello,
I am assigning the dependencies as you described:
“To do what you want, you’ll have to make the 2nd job dependent on the 1st, the 3rd on the 2nd, and the 4th on the third.”
but deadline does not respect the dependencies chain.
other thing what i tried was to :
2nd job dependent to 1st
3th job dependent to 2nd AND 1st
4th job dependent to 3nd AND 2nd AND 1st
but this does not work either…
sometimes the jobs just stay on pending and sometimes they run all at the sametime when the first job in the chain is finished…
Thanks for confirming. We ran some tests here and were able to reproduce issues with the dependencies. These issues will be fixed in beta 5, which we hope to release later this week. You’ll have to test with beta 5 and let us know if you continue to have problems with dependencies.
Thanks for reporting this!
thanks for the update! it works much better now and respects the chain.
but other bug : it still does not respect the chain of dependencies when the “IsFrameDependent” is set to “true”. then it runs all the dependencies at the same time
but when “IsFrameDependent” is “false” it works
Thanks for reporting the frame dependencies problem! We were able to reproduce it, and it will be fixed in beta 6.
Cheers,