Hmm, the error you're seeing is unrelated to notes submitted to the job..
so in other words this:
> notes COMMAND: render -Va /out/ROP_cloves_noholdout
..is not related to this:
> "rush: 'rush -notes': frame range error: 'retry': bad frame number at 'r'"
I'm assuming you're seeing that error message in the frame log,
correct? ie. after the houdini render fails in some way.
I'm thinking the latter error message is a malformed 'rush -notes'
command in the python script that is trying to set the "frame notes"
(not the "job notes") to show a retry count message in the Frames report.
In your script, look for a 'rush -notes' or 'rush -fu -notes' command
and let's take a look at the python code that forms it.
I'm thinking the frame number is absent from the command,
as it should be trying to form a command that looks something like this:
rush -fu -notes 0055:"retry #1 of 3"
..where:
> "0055" is the os.environ["RUSH_FRAME"]
> '1' is the try count,
> '3' is the maximum retry count the user specified
I'm thinking the "0055:" is being left out.
On 07/22/13 16:16, Mr. Daniel Browne wrote:
> Hi Greg,
>
> I'm trying to get rid of a long standing bug in my python-based Houdini scripts. The hbatch command is passed via the Notes field, just as it is in your perl version of the script. According to your docs however the notes field needs to begin with a frame range, correct?
>
> Here's a submit which illustrates the current state of my notes field:
>
> title cca0030_fx_cloves_007_v001.hip-ROP_cloves_noholdout_HOUDINI
> frames 1398-1578,1000000
> command python /EEP/Tools/Settings/rush/rushscripts_v102.42a9/submit-maya-python/submit_houdini.py -render /Casino/Poker/Shows/cc/cca/cca0030/fx/houdini/chrish/cca0030_fx_cloves_007_v001.hip 0 off 1000000 1578 1 yes 3 Fail
> imgcommand python /EEP/Tools/Settings/rush/rushscripts_v102.42a9/submit-maya-python/submit_houdini.py -imgcommand %s
> autodump off
> maxtime 00:00:00
> maxtimestate que
> ram 8000
> waitforstate done
> cpus +linux=1@10
> logdir /Casino/Poker/Shows/cc/cca/cca0030/fx/houdini/chrish/logs/cca0030_fx_cloves_007_v001.hip.log/ROP_cloves_noholdout
>
> notes COMMAND: render -Va /out/ROP_cloves_noholdout
>
> This typically produces an error and causes the render to immediately go to retry #2:
>
> "rush: 'rush -notes': frame range error: 'retry': bad frame number at 'r'"
--
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)
|