[Buildbot-devel] Jumping over the next "addStep"

[Nikunj Badjatya]

Dear fulvio,

Thanks for the comments.
I want to provide lil more information about the scenario.

"execution.sh" is actually callling many other scripts. These other scripts
actually build the testcases which tests some api's on diff diff
architectures. ( x86, mips, arm ). sometimes it happens that a particular
testcase ( say  binary of 1.c ) hangs because of some kinda shell
environment / resources issue. Now it is very unlikely that the testcases
getting hanged is preknown to user. Also the average amount of time a
testcase use to complete is also varying. !! Thus using "timeout" for any
particular testcase or for particular period wont solve the problem. !!

I hope I am clear.

The only solution being feasible to me is "kill" where shell scripts
"called.sh" is running. So that the buildmaster will continue executing
"execution.sh" till it lasts.
I just want to make it more easier as without killing.. jump to next build
addStep. !


---------------------------

If anyone has a different and efficient solution  please reply.!!


Thanks,

Nikunj
Bangalore, India



On Mon, May 16, 2011 at 12:14 PM, Fulvio Cervone <fcervone at me.com> wrote:

> If is a shell script you can implement a function in the script itself, so
> if it takes more than X amount of time, it will exit with code 1; this will
> result in the step to quit and mark the step as failed (then you can decide
> if the whole build fail or not using the step parameters).
>
> Another way is to use properties; probably some other user can point out
> some good example, since the manual has only a simple case.
>
>
> On May 15, 2011, at 11:31 PM, Nikunj Badjatya wrote:
>
> Hi,
>
> I am using :
>
> *Buildbot version: 0.7.12
> Twisted version: 9.0.0
> Python ver 2.6.6
> CentOS 5.6*
>
> I have a question regarding addStep function. Suppose there is one
> 'f.addStep( )' which uses 'shell.ShellCommand(..)'. If a shell command is
> taking too much time to reach its completion. Its usual execution time is
> not fixed and varies as per source taken. So using 'timeout' of 'maxTime'
> is of no use.
> Now I want to jump over this particular 'addStep' to start next 'addStep' .
> !
> How I can accomplish this functionality. ??
>
> {{{
> Ex.
> *f.addStep( shell.ShellCommand( workdir=basedir, command="./execution.sh ;
> ", timeout = 6000, description=["Doing execution"], descriptionDone=["Done
> execution"])*
>
> now *execution.sh* taking too much time to complete. And I want to jump to
> next step which could be anything else.
>
> *f.addStep( shell.ShellCommand( workdir=basedir, command="./next.sh ; ",
> timeout = 6000, description=["Doing next"], descriptionDone=["Done next"])
> *
>
> }}}
>
> Please let me know how this can be accomplished. !!
>
>
> Thanks,
>
> Nikunj
> Bangalore, India
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
>
> http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20110518/e510918f/attachment.html>