Next step may be increasing the debugging/logging. Are there any other
test stanzas?
What happens if you run all the same steps locally?
On Tuesday, April 24, 2012 6:32:30 PM UTC-4, RatedAbstract wrote:
>
> Hi Andrew,
>
> That plugin was indeed installed. I disabled this plugin, restarted
> Hudson, but still I see that jobs are finishing after an hour. Following is
> the ant build file that I'm using, I've also specified timeout to be 3
> hours, but it doesn't seem to be working. Any idea?
>
> <!-- maximum total time in milliseconds (3 hours) for all tests to run,
> over-writing default of 60 minutes -->
> <property name="testng.timeOut" value="10800000"/>
>
>
> <target name="run-tests" depends="test-compile,
> testng.xml.fileset.check" unless="testng.xml.fileset.run">
> <testng suitename="abc"…
> *timeOut="${testng.timeOut}"*dumpCommand="true">
>
> …
> <echo message="From first run: unitTest.failure =
> ${unitTest.failure}" />
> </target>
>
> Thanks
>
> On Monday, April 23, 2012 10:56:26 PM UTC-7, Andrew Harley wrote:
>>
>> Hi,
>>
>> There is a plugin which provides similar results to what you're seeing:
>>
>> https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin
>>
>> Perhaps this addon is installed and enabled on all jobs.
>>
>> Andrew
>>
>> ------------------------------
>> *From:* jenkinsci-users@googlegroups.com [mailto:
>> jenkinsci-users@googlegroups.com] *On Behalf Of *RatedAbstract
>> *Sent:* Tuesday, 24 April 2012 3:28 PM
>> *To:* jenkinsci-users@googlegroups.com
>> *Subject:* Increasing Hudson job time
>>
>> Hi,
>>
>> My Hudson jobs are running on a daily schedule. All of the jobs stop
>> after an hour... So, it builds, runs tests, but tests that fall outside of
>> this one hour interval window don’t run.
>>
>> Does anyone know how to increase this one hour time limit?
>>
>> Thanks
>>
>>
