Author Topic: Qube determining failures  (Read 1418 times)

ashok

  • Full Member
  • ***
  • Posts: 11
Qube determining failures
« on: March 02, 2013, 01:21:26 AM »
We have some Nuke jobs that have been reporting all the frames to have failed when they have in fact been writing out frames successfully. We have some errors in the log that are thrown from client nodes and we think this may be causing the false failures to be reported.

How does Qube determine what a failure is? Is it possible to tell Qube to ignore specific errors? Any help is greatly appreciated.

Thanks!

BrianK

  • Hero Member
  • *****
  • Posts: 107
Re: Qube determining failures
« Reply #1 on: March 03, 2013, 11:15:26 PM »
Qube checks the exit status of the application.  If the application exits in error, the frame is marked as failed.  The fact that an image exists is not a sign of success (and I will argue that this is correct behavior).

For Nuke, there is not currently a way to ignore these errors, at least on the Qube side of things.  You could write a wrapper script for Nuke that always exits with a 0 exit status & have Qube run that wrapper script instead of the Nuke executable.