Oh gosh. That's why my debugging prints didn't appear... I was using job.parallel and debugging utils.run_parallel...
Thanks for the quick reply. On Mon, 2010-07-19 at 12:15 -0500, Shaun Ruffell wrote: > On 07/19/2010 12:01 PM, Rafael Folco wrote: > > Hello core developers, > > > > I need some help debugging run_parallel function, I think we have a bug > > there. I am using job.parallel and I have a hard time to get return code > > from it. It looks like this function is not returning anything, it is > > always as 'None'. > > > > In client/common_lib/utils.py I took a look at run_parallel function, > > but I could not find where the problem is: > > job.parallel (implemented in client/bin/job.py) has a different > implementation that run_parallel in client/common_lib/utils.py, and it > doesn't return any value. > > Instead of job.parallel, try, utils.run_parallel. > > _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
