Just wanted to post this to see if anyone is having the same issues. This machine continued to render despite the fact that it was configured within the repository options to be marked as bad after 5 errors.
Any ideas? I’ve attached an image as well.
Thanks!
This bug should be fixed in beta 5, and your current version is beta 4. Upgrading to the latest beta should address the issue.
Note that we are planning to release a new beta early next week, so you might want to wait if you can live with this bug for now.
Cheers,
- Ryan
Alright, I’ll be looking forward to the fix! Thanks!
I tried pushing deadline 6.52823 on to our farm yesterday, and we still see the same results. We’re rendering max files on Windows 7.
In your Failure Detection settings in the Repository Options, what do you have set for the “Frequency at which a slave will attempt a job that it has been marked bad for”? The default is 5%, which means that a slave will attempt a job it’s been marked bad for 5% of the time if there are no “good” jobs remaining. Maybe try setting it to 0 (if it’s not already) to see if that makes a difference.
I tested with both beta 6, and our current internal version, and in both cases, the bad slave detection seemed to be working properly…