From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: Bug with jobdonecommand/dump?
   Date: Wed, 25 Jun 2008 00:55:49 -0400
Msg# 1765
View Complete Thread (6 articles) | All Threads
Last Next
Abraham Schneider wrote:
Hi!

We updated to the new version last week. FIFO seems to work very fine=20
and helps alot for our situation here! Thanks for that!

But today I recognized a strange behaviour with rush. I'm not sure if=20
this is a 'bug/feature' of the new version or if this is an old=20
behaviour. When I dump a job which hasn't finished yet, there is a=20
moment where there is the text in the remarks of this job that it=20
executes the jobdonecommand.

    Thanks Abraham -- I'll have to check into this to see if this
    is intended behavior or not, and if not, at what point it crept in,
    and fix it.

    When I find out more, I may come out with a follow up fix release
    to solve it.

    I can confirm 'jobdonecommand' is indeed being executed when a job
    is dumped even if the frames have not finished.

    For the short term, your jobdonecommand can look at the 'framelist'
    file to determine if there were unfinished frames or not.

    When I return next week, I'll definitely look into this.

    One question: what version of Rush did you upgrade /from/?

Is this an intentional behaviour or a bug? For me, it makes no sense to=20
execute a script/command in this situation which is meant to run when=20
the job has finished rendering completely without any problems.

    Actually, I need to check to see if the docs ever said that the
    jobdonecommand command would not be run if there were any 'Fail'
    frames -- I'm not sure that's the case.

    I'd agree certainly the jobdonecommand shouldn't be executed there
    are still frames in the "Que" or "Hold" state.

    But whether any frames were 'Fail'ed or not, the jobdonecommand
    can look at the framelist or 'rush -lf/-lfi' report to make that
    determination.

    There may be cases where it's desirable for the jobdonecommand
    to be executed even if some frames Fail(ed), such as generating
    a Quicktime with the failed frames replaced with "X" frames
    to give the TDs a hint as to which frames failed, and to go back
    and check the logs for those frames to see what went wrong.

    What I should maybe do is add a flag for the jobdonecommand
    that defines whether rush should execute the command only
    if all the frames are 'Done', or 'Done/Fail'.

--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

     ********************  N O T I C E  *************************
     ***   I'll be on vacation June 18th through June 28th.   ***
     ***   During this time I will be watching email, but it  ***
     ***   may take up to a day for me to reply.              ***
     ************************************************************

Last Next