On Mon, Aug 11, 2008 at 6:24 PM, Jim Weirich <[EMAIL PROTECTED]> wrote: > > On Aug 11, 2008, at 9:35 AM, Ittay Dror wrote: > >> Note that the current use of threads, in either MultiTask, or the JobTask >> I sent earlier is faulty. Imagine tasks A, B, C, D where A => [B, C], >> B=>[D], C=>[D]. Now if B and C are invoked in parallel, C invokes D which >> fails. C promptly fails. B continues to run and to it D seems to have been >> already invoked, so it does its actions assuming D's actions were executed >> which isn't true. > > > Do we need some kind of error state, eg. invoked, but failed?
My initial suggestion is to linearize the invocation process. Then, if a task fails, Rake stops the execution. If a developer wants the execution to continue even if some actions fail, he writes those actions such that they return normally (begin...rescue). > > -- > -- Jim Weirich > -- [EMAIL PROTECTED] > > _______________________________________________ > Rake-devel mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rake-devel > _______________________________________________ Rake-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/rake-devel
