From: Gary Jaeger <gary@(email surpressed)> Subject: Job Edit Date: Fri, 19 Aug 2011 12:09:35 -0400 |
Msg# 2119 View Complete Thread (3 articles) | All Threads Last Next |
I'm confused by the Job Edit.. function. Let's say I submit a job with a fail time set to 5:00. Most frames render but a few don't. So I do Job Edit... and change the fail time to 10:00 and re-que those frames. But they still fail at 5:00. Is that how it's supposed to work? . . . . . . . . . . . . Gary Jaeger // Core Studio 86 Graham Street, Suite 120 San Francisco, CA 94129 (Tel# suppressed) http://corestudio.com |
From: Greg Ercolano <erco@(email surpressed)> Subject: Re: Job Edit Date: Fri, 19 Aug 2011 12:54:43 -0400 |
Msg# 2120 View Complete Thread (3 articles) | All Threads Last Next |
On 08/19/11 09:09, Gary Jaeger wrote: > I'm confused by the Job Edit.. function. Let's say I submit a job with a = > fail time set to 5:00. Most frames render but a few don't. So I do Job = > Edit... and change the fail time to 10:00 and re-que those frames. But = > they still fail at 5:00. > Is that how it's supposed to work? Hmm, no, it should take effect right away. Even frames that are in progress should be affected, as the job server keeps track of managing frame maxtimes. Are you sure after you change the value in job edit, if you go back into job edit, does it still show the old value? Perhaps there's a complaint about not being the job owner, preventing job edit from making your changes. (ie. if you're editing someone else's job, be sure to enable the FU mode) If not and this is repeatable, it would be good if you could show me some reports showing the problem. For instance, I tried to replicate this here, but it seems to work OK, even in irush. Here I submit a job that takes 40 secs per frame, but set the maxtime to 30, and it keeps requeing. Then I change the timeout to 50, then it runs OK: % ( echo frames 1-50 ; echo command sleep 40 ; echo cpus tahoe; echo maxtime 00:00:30 ) | rush -submit setenv RUSH_JOBID ta.106 % setenv RUSH_JOBID ta.106 % rush -lf | head -3 Status Frame Try Hostname Pid Jobid Start Elapsed Notes Run 0001 0 ta 7805 ta.106 08/19,09:43:43 00:00:29 - <-- 29 secs Que 0002 0 - 0 ta.106 00/00,00:00:00 00:00:00 - % rush -lf | head -3 Status Frame Try Hostname Pid Jobid Start Elapsed Notes Run 0001 1 ta 7830 ta.106 08/19,09:44:20 00:00:00 - <-- always resets at 30 secs Que 0002 0 - 0 ta.106 00/00,00:00:00 00:00:00 - % rush -maxtime 00:00:50 <-- change timeout to 50 secs (renders take 40 secs) ta.106: maxtime is now '00:00:50' % rush -lf | head -3 Status Frame Try Hostname Pid Jobid Start Elapsed Notes Done 0001 3 ta 7971 ta.106 08/19,09:50:48 00:00:41 - <-- finishes Done 0002 1 ta 8000 ta.106 08/19,09:51:30 00:00:41 - <-- finishes -- 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) |
From: Gary Jaeger <gary@(email surpressed)> Subject: Re: Job Edit Date: Fri, 19 Aug 2011 13:53:27 -0400 |
Msg# 2121 View Complete Thread (3 articles) | All Threads Last Next |
I'll check and get back to you On Aug 19, 2011, at 9:54 AM, Greg Ercolano wrote: > Hmm, no, it should take effect right away. . . . . . . . . . . . . Gary Jaeger // Core Studio 86 Graham Street, Suite 120 San Francisco, CA 94129 (Tel# suppressed) http://corestudio.com |