OK now this bug is quite specific and technical.
Deadline Version: 10.1.4.1
We are planning to update soon, but just wanted to know if this is still an issue.
Context:
I have a very simple Event that modify the frame range of a job when submitted.
Problem:
But for some reason, when I change the frame range using RepositoryUtils.SetJobFrameRange
The job goes to “Pending”.
I’m like ok this is a bug, I can check the Status after changing the frame range in the Event and if it’s “Pending”, release it! But no, if I do job.JobStatus
after changing the frame range, it says the status is still “Active” (Which is Queued.)…?? But in reality it’s “Pending”. (This is another bug!)
What cause the problem:
So I found out if the job is submitted as “Frame Dependent” (which is by default in Houdini for example) and you wanna change the frame range using RepositoryUtils.SetJobFrameRange
, the problem occurs! The job before the Event was “Queued” and not “Pending”.
Expected behavior:
If you change the frame range of a job in Python, the Job Status should be:
- Queued if was Rendering/Queued
- Suspended if was Suspended
- Pending if was Pending
- Failed if was Failed
You know the drill
TD;DR: Using Python in an Event, If a job is “Queued” and “FrameDependent” is activated, when you change it’s frame range in Python, the job goes to “Pending” even if it was “Queued” in the first place.