Time Out Strategy Question

[Mabry Dozier]

Our tests are run based on SVN changes, and often are minor changes that build quickly.   Once the compilation is completed, we then run a series of tests on the executable just built.     

We want to set a time out condition (using time out strategy) to stop a test that hangs and mark as failed.    

At present, use use the "elastic" timeout since the length of time for this process can be quite variable.

From time to time code changes require a much more significant re-build which extends the time significantly.   Once several shorter times are run, the elastic time is then too short for a more lengthy run.

We are getting timeouts in the middle of active system compilations, based on the elastic time.     Note that our builds can be run on several slaves, so the current last built state can be different from slave to slave.

Any ideas to resolve this?

Thanks in advance,

Mabry

[Baptiste Mathus]

Do not use elastic strategy? Use a hard coded value?

Cheers

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0be05afb-6b61-4c30-8876-f60387639203%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.