On 05/04/12 14:53, Greg Ercolano wrote:
> On 05/04/12 14:06, Mr. Daniel Browne wrote:
>> I'll let you know what I find next time it occurs. It seems to only =
>> happen with jobs running on a specific group of machines that are being =
>> used for GPU-accelerated rendering.
>
> Mmm, I'd be surprised if that mattered; use of GPU or otherwise
> shouldn't affect a process's execution.. unless that is it's
> running in an 'unkillable' state while interacting with the hardware.
>
> Let's wait to see what you find.
Actually, you might try to replicate from the command line;
try running your python script with the same command you're
telling rush to run. (Just set any RUSH environment variables
the script depends on, like RUSH_FRAME or RUSH_JOBID).
Then, while it's rendering, hit ^C to kill it,
then check to see if somehow the render is still running.
So for instance, if you're telling rush to run:
python /your/script/foo.py -render -arg1 -arg2 -arg3
..then to test from the command line, use e.g.
( export RUSH_FRAME=1; export RUSH_JOBID=yourjobid.123; python /your/script/foo.py -render -arg1 -arg2 -arg3 )
..before hitting ^C.
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|