> Cc: infra@ovirt.org
> > > Sent: Monday, February 9, 2015 10:06:14 PM
> > > Subject: Re: constantly failing
> > > http://jenkins.ovirt.org/job/vdsm_master_unit_tests_gerrit_el
> > >
> > > On Fri, Feb 06, 2015 at 05:56:18PM +0100, David Caro wrote:
On Tue, Feb 10, 2015 at 05:55:25AM -0500, Francesco Romani wrote:
> - Original Message -
> > From: "Dan Kenigsberg"
> > To: "David Caro" , from...@redhat.com
> > Cc: infra@ovirt.org
> > Sent: Monday, February 9, 2015 10:06:14 P
- Original Message -
> From: "Dan Kenigsberg"
> To: "David Caro" , from...@redhat.com
> Cc: infra@ovirt.org
> Sent: Monday, February 9, 2015 10:06:14 PM
> Subject: Re: constantly failing
> http://jenkins.ovirt.org/job/vdsm_master_unit_tests_gerrit
On Fri, Feb 06, 2015 at 05:56:18PM +0100, David Caro wrote:
>
> I've retaken the work on that job, I've got it mostly working but there are a
> few tests failing:
>
>
> http://jenkins.ovirt.org/job/vdsm_master_unit-tests_created_staging/435/console
>
>
> Can someone from your team take a look?
I've retaken the work on that job, I've got it mostly working but there are a
few tests failing:
http://jenkins.ovirt.org/job/vdsm_master_unit-tests_created_staging/435/console
Can someone from your team take a look? I'll update the tracker also (I think
yeela is cc'd there).
On 01/28, Dan Ke
On Tue, Jan 20, 2015 at 01:14:03PM +, Dan Kenigsberg wrote:
> On Tue, Jan 20, 2015 at 10:09:12AM +0100, David Caro wrote:
> >
> > I vaguely recall that we already talked about this, and someone
> > started working on it.
> >
> > The issue is that it's trying to use the tests output, but the r
On Tue, Jan 20, 2015 at 10:09:12AM +0100, David Caro wrote:
>
> I vaguely recall that we already talked about this, and someone
> started working on it.
>
> The issue is that it's trying to use the tests output, but the run
> does not generate any (that was a feature change in the python test
> m
I vaguely recall that we already talked about this, and someone
started working on it.
The issue is that it's trying to use the tests output, but the run
does not generate any (that was a feature change in the python test
module that it uses).
"""
Recording test results
No test report files were
The job on $subject constantly reports failure, regardless of successful
output.
http://jenkins.ovirt.org/job/vdsm_master_unit_tests_gerrit_el/14286/console
Ran 801 tests in 94.766s
OK (SKIP=57)
...
Recording test results
No test report files were found. Configuration error?
Build step 'Publish
