- Original Message -
> From: "Dan Kenigsberg"
> To: "Eyal Edri"
> Cc: "Deepak C Shetty" , "Saggi Mizrahi"
> , "infra"
> Sent: Sunday, January 27, 2013 1:21:38 PM
> Subject: Re: Jenkins build failure due to "publish of test report" failing
>
> On Sat, Jan 26, 2013 at 11:53:36AM -0500,
- Original Message -
> From: "Roy Golan"
> To: infra@ovirt.org
> Sent: Sunday, January 27, 2013 2:06:40 PM
> Subject: Re: [JENKINS] important change in findbugs analysis
>
> On 01/27/2013 11:57 AM, Eyal Edri wrote:
> > fyi,
> >
> > as part of the efforts to reduce bugs found by findbugs
On 01/27/2013 11:57 AM, Eyal Edri wrote:
fyi,
as part of the efforts to reduce bugs found by findbugs jenkins job,
NORMAL priority bugs limit has been set to 15 (current count),
this means that any NEW NORMAL bugs that will enter ovirt-engine code will fail
the job,
and it's the committer respo
On Sat, Jan 26, 2013 at 11:53:36AM -0500, Eyal Edri wrote:
>
>
> - Original Message -
> > From: "Dan Kenigsberg"
> > To: "Eyal Edri"
> > Cc: "Deepak C Shetty" , "Saggi Mizrahi"
> > , "infra"
> > Sent: Saturday, January 26, 2013 3:55:05 PM
> > Subject: Re: Jenkins build failure due to
fyi,
as part of the efforts to reduce bugs found by findbugs jenkins job,
NORMAL priority bugs limit has been set to 15 (current count),
this means that any NEW NORMAL bugs that will enter ovirt-engine code will fail
the job,
and it's the committer responsibility to fix it.
if you're not sure
### Logwatch 7.3.6 (05/19/07)
Processing Initiated: Sun Jan 27 03:33:13 2013
Date Range Processed: yesterday
( 2013-Jan-26 )
Period is day.
Detail Level of Output: 0
