ovirt-engine build failure

Alon Bar-Lev alonbl at redhat.com
Tue Feb 18 09:45:55 UTC 2014



----- Original Message -----
> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: "Juan Hernandez" <jhernand at redhat.com>, "Kiril Nesenko" <knesenko at redhat.com>, "Eyal Edri" <eedri at redhat.com>,
> "David Caro" <dcaroest at redhat.com>, "arch" <arch at ovirt.org>
> Sent: Tuesday, February 18, 2014 11:43:13 AM
> Subject: Re: ovirt-engine build failure
> 
> Il 18/02/2014 10:37, Alon Bar-Lev ha scritto:
> > 
> > 
> > ----- Original Message -----
> >> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> >> To: "Alon Bar-Lev" <alonbl at redhat.com>
> >> Cc: "Juan Hernandez" <jhernand at redhat.com>, "Kiril Nesenko"
> >> <knesenko at redhat.com>, "Eyal Edri" <eedri at redhat.com>,
> >> "David Caro" <dcaroest at redhat.com>, "arch" <arch at ovirt.org>
> >> Sent: Tuesday, February 18, 2014 11:36:29 AM
> >> Subject: Re: ovirt-engine build failure
> >>
> >> Il 18/02/2014 09:49, Alon Bar-Lev ha scritto:
> >>>
> >>>
> >>> ----- Original Message -----
> >>>> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> >>>> To: "Juan Hernandez" <jhernand at redhat.com>, "Alon Bar-Lev"
> >>>> <alonbl at redhat.com>
> >>>> Cc: "Kiril Nesenko" <knesenko at redhat.com>, "Eyal Edri"
> >>>> <eedri at redhat.com>,
> >>>> "David Caro" <dcaroest at redhat.com>, "arch"
> >>>> <arch at ovirt.org>
> >>>> Sent: Tuesday, February 18, 2014 10:13:54 AM
> >>>> Subject: ovirt-engine build failure
> >>>>
> >>>> Hi, we hit again an issue that comes up really often while building
> >>>> ovirt-engine in jenkins,
> >>>> especially when we're in a hurry because we're releasing.
> >>>>
> >>>> http://jenkins.ovirt.org/job/manual-build-tarball/212/label=fedora19-host/console
> >>>>
> >>>> IIRC it may be a corrupted artifact or an error in maven dependency
> >>>> resolution.
> >>>> Can we find a way for having it fixed once for ever?
> >>>
> >>> We are using a local artifactory mirror, so having corruption is
> >>> unlikely.
> >>> I think that maven checks sha1 of artifacts and reports corruption issue
> >>> before trying to use.
> >>> In this case something is failing at gwt generation, I am unsure if it is
> >>> not related to resources.
> >>
> >> The weird thing is that it may fail on the same point for a tenth of times
> >> and then build successfully on the exact same host.
> >> And that's the only job running on a 4 core i7 processor with 16 GB of
> >> ram.
> > 
> > With or without cleaning up the workspace?
> 
> without

Still looks like resource issue... as if there is corrupted artifact it will be reused.

> 
> 
> > 
> >>
> >>
> >>>
> >>>>
> >>>>
> >>>> --
> >>>> Sandro Bonazzola
> >>>> Better technology. Faster innovation. Powered by community
> >>>> collaboration.
> >>>> See how it works at redhat.com
> >>>>
> >>
> >>
> >> --
> >> Sandro Bonazzola
> >> Better technology. Faster innovation. Powered by community collaboration.
> >> See how it works at redhat.com
> >>
> 
> 
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 



More information about the Arch mailing list