rendering: not in batch mode
We are noticing that nuke’s exit code is 0, but its actually erroring out mid frame, so deadline is not detecting the error and simply marks the frame complete. Have you guys seen this before?
Can you post a log from the job that shows this happening? Maybe there is an error we simply aren’t catching.
Thanks!
- Ryan
Attached are two logs.
Please note that these are erroring now because we implemented a workaround. Sally added a simple print to the closenuke event, and the nuke.py deadline plugin fails the job if it does not see that line being printed. Its a terrible workaround that will make it very hard to switch to batch mode (if we ever end up doing that), but it seems to catch these cases.
Note that the exit code is 0 in both cases:
2013-12-04 10:23:55: 0: INFO: Process exit code: 0
slave_log2_nuke_bad_exit_code.txt (15.5 KB)
slave_log_nuke_bad_exit_code.txt (143 KB)
Hmm, there isn’t anything in those logs to tell Deadline that an error occurred. Have you guys mentioned this issue to the foundry? It’s strange that Nuke would return 0 and not print out an error when a frame fails to finish rendering.