[SOLVED] Best methods of retrieving std from sub-processes of Python plugin from virtualenvs

Deadline
1

Hi there,

We’re invoking custom Python command-lines and have some processes which after being launched in a contained virtual environment don’t appear to be able to log their progress back into the Deadline Plugin’s logging system itself.

Is there any recommended practices for this so we don’t have to log to file on disk to find out what’s going in within said virtualenv?

Note: We may have resolved this ourselves, please delete/demote this post.

Cheers

Jamie

2

I’d rather you explain how you fixed it! :smiley:

I can delete it if I must.

1 Like
3

Hi Edwin,

Sure, appreciate an explanation would more helpful here.

So we have a unified environment launch system which spawns virtual environments which, in some cases, spawn another task/process. This system ensures our application’s environment is consistent throughout our entire pipe when on desktop, the farm or the cloud.

In the earlier builds of Deadline (10.0.11.x or there about) we noted that some of the standard out logging to console was acting peculiar with the Deadline client logging systems internally.

Turns out we muted some of the pipe outs on some of the spawned child tasks and when we re-enabled them recently (aka our solution we’re testing with now) appear to be verbosing the std out as hoped.

Hope this helps as we’ve not really done much to change things so can only speculate that Deadline Client 10.0.21.5 is more stable for us!

cheers

Jamie

1 Like