Jenkins ovirt-engine DAO Test Job

[Eyal Edri]

----- Original Message -----
> From: "Eyal Edri" <eedri at redhat.com>
> To: "Itamar Heim" <iheim at redhat.com>
> Cc: infra at ovirt.org
> Sent: Thursday, March 22, 2012 9:33:36 AM
> Subject: Re: Jenkins ovirt-engine DAO Test Job
> 
> 
> 
> ----- Original Message -----
> > From: "Itamar Heim" <iheim at redhat.com>
> > To: "Moti Asayag" <masayag at redhat.com>
> > Cc: infra at ovirt.org, "Eyal Edri" <eedri at redhat.com>
> > Sent: Thursday, March 22, 2012 4:55:36 AM
> > Subject: Re: Jenkins ovirt-engine DAO Test Job
> > 
> > On 03/22/2012 02:10 AM, Moti Asayag wrote:
> > > Hi,
> > >
> > > Seems that DAO Test job is stuck:
> > >
> > > http://jenkins.ovirt.org/job/ovirt_engine_dao_unit_tests/394/console
> > >
> > > Could this Job be restarted ?
> > 
> > do we use the build-timout plugin to monitor hung jobs?
> > 
> 
> we do. it was set to 300 min. but didn't work.
> i will send a bug on it to the plugin developer.

according to the plugin documentation, the abort will not work in certain situations:

Because Java only allows threads to be interrupted at a set of fixed locations, depending on how a build hangs, the abort operation might not take effect. For example,
if Jenkins is waiting for child processes to complete, it can abort right away.
if Jenkins is stuck in an infinite loop, it can never be aborted.
if Jenkins is doing a network or file I/O within the Java VM (such as lengthy file copy or SVN update), it cannot be aborted.
So if you think the build time out isn't taking effect, our default assumption is that the build is hanging at the place that cannot be interrupted. If you suspect otherwise, please obtain the thread dump and report it.

i will need to take the threadDump next time it happens and see if it's a bug.



> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>