probably. it's a new jenkins vm. set it to run for now on the 2nd f17 slave.
thanks, Eyal. ----- Original Message ----- > From: "Dan Kenigsberg" <dan...@redhat.com> > To: "Eyal Edri" <ee...@redhat.com> > Cc: aba...@redhat.com, vdsm-patches@lists.fedorahosted.org > Sent: Wednesday, June 20, 2012 5:09:37 PM > Subject: Re: [oVirt Jenkins] vdsm_unit_tests - Build # 219 - Failure! > > On Wed, Jun 20, 2012 at 08:56:57AM -0400, Jenkins oVirt Server wrote: > > > > BUILD FAILURE > > Build URL: http://jenkins.ovirt.org/job/vdsm_unit_tests/219/ > > Project: vdsm_unit_tests > > Date of build: Wed, 20 Jun 2012 08:56:34 -0400 > > Build duration: 22 sec > > > > CHANGE SET > > Revision 0f4ad8a01eb0dcc03ef4633afef2465d5082d6c5 by danken: > > (deployUtil.yumFind: rename and simplify semantics) > > change: edit vdsm_reg/deployUtil.py.in > > Revision af04764b03cdb767e83a773e959ddf2e91c1981e by danken: (drop > > deployUtil.yumSearch) > > change: edit vdsm_reg/deployUtil.py.in > > change: edit vds_bootstrap/vds_bootstrap.py > > Revision e1c486f8fc483a36d8b82dcd6464d0966a8e5e8d by danken: > > (deployUtil.yumSearchVersion: compare versions sanely) > > change: edit vds_bootstrap/vds_bootstrap.py > > change: edit vdsm_reg/deployUtil.py.in > > Could it be that this slave does not have autoconf/autmake installed? > > + ./autogen.sh --system > ./autogen.sh: line 3: autoreconf: command not found > _______________________________________________ vdsm-patches mailing list vdsm-patches@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-patches