river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sim IJskes - QCG <...@qcg.nl>
Subject Re: Build failed in Hudson: River-trunk-QA #40
Date Mon, 01 Nov 2010 16:29:28 GMT
On 11/01/2010 05:21 PM, Jonathan Costers wrote:
>  From what I can see, this started at QA build #34, which was aborted.
> When aborting a QA build, you will leave open resources, depending on what
> was running at the time of abortion.
> There is no easy way around this (that I can think of), but to avoid
> aborting QA builds, especially on Hudson.
> If you do, you will have to manually kill some processes or reboot.

OK, suggestion: We will make a lockfile with a timestamp. In every test 
VM we start a process that check for existance of this file every say 1 
minute. When its gone, call System.exit(1); We will start every QA with 
removal of all the lockfiles, and wait for 2 minutes. Then create a new 
lockfile, pass it in the environment for the testvm's to pick up when 

And maybe we could even use the hudson locking stuff for it.

Gr. Sim

View raw message