AWS Thinkbox Discussion Forums

cancel current task from commandline WITH log

Deprecated Deadline 6 Beta Discussion
#1

Is it possible to cancel the current task of a specified slave, with a defined log message to be added to the log?

We have to kill slaves in certain cases, where kill the tasks would be enough, but we need to be able to add something to the logs about why this happened (otherwise it sends the artist, wranglers, pipeline tds on the hunt for something that was actually proper behavior)

#2

This currently isn’t possible. We’re currently working on including slave logs with requeue reports for 7.0, and in theory this should open the door to allow something like this to work. We’ll log this as a feature request targeting 7.0 for now, and evaluate it later to see if it’s something we can actually do for 7.0.

Thanks!
Ryan

#3

Is it possible to implement this in either the nuke or 3dsmax plugins ourselves? We could set up some kind of a system where the existence of a token file would be monitored, and if it appears, the plugin would kill the task. A hack but might work? I just dont know if the plugin scripts are ‘live’ while max/nuke is rendering or not…

#4

You could definitely add this to the 3dsmax plugin, since the plugin script loops while waiting for the render to finish (PollUntilComplete). With Nuke, this would currently only work in batch mode, otherwise the script is just used to get the executable and the arguments for the command line render and won’t be “live” during the render.

If you can’t use batch mode in Nuke, it should still be possible to create a ManagedProcess class that wraps the Nuke command line render and then when looping while waiting for it to finish, you can do the the memory checks in addition to the popup and stdout handling that is required (you can refer to the PollUntilComplete function in 3dsmax.py).

Cheers,
Ryan

#5

I’ve noticed this in the release candidate notes:

Scripting Improvements

  • Added API functions to log job, slave, or history entries.

Does this mean we could use the python API to add something to the log before killing the task? Or the task log is not accessible (only job slave & history)

#6

No, just the job and slave history are accessible though this.

Cheers,
Ryan

Privacy | Site terms | Cookie preferences