-Original Message-
From: Hugo Trippaers [mailto:trip...@gmail.com]
Sent: Friday, 21 February 2014 1:15 AM
To: dev@cloudstack.apache.org
Cc: dev@cloudstack.apache.org; Hugo Trippaers; Ian Southam
Subject: Re: Master blocker CLOUDSTACK-6130
Sent from my iPhone
> On 20 feb. 2014, at
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Thursday, February 20, 2014 5:45 AM
> To:
> Cc: Hugo Trippaers; Ian Southam
> Subject: Re: Master blocker CLOUDSTACK-6130
>
> Hey,
>
>
Sent from my iPhone
> On 20 feb. 2014, at 18:31, Srikanteswararao Talluri
> wrote:
>
>
>
>> On 20/02/14 7:14 pm, "Hugo Trippaers" wrote:
>>
>> Hey,
>>
>> Should be fixed by:
>> commit ba7ff5369cc602c7e0c8d788b6617f27123c2328
>> Author: Hugo Trippaers
>> Date: Thu Feb 20 14:04:51 2014
On 20/02/14 7:14 pm, "Hugo Trippaers" wrote:
>Hey,
>
>Should be fixed by:
>commit ba7ff5369cc602c7e0c8d788b6617f27123c2328
>Author: Hugo Trippaers
>Date: Thu Feb 20 14:04:51 2014 +0100
>
>Fix parameter index in getCount function.
>
>
>@Talluri, Agreed. However with the current way of te
Hey,
Should be fixed by:
commit ba7ff5369cc602c7e0c8d788b6617f27123c2328
Author: Hugo Trippaers
Date: Thu Feb 20 14:04:51 2014 +0100
Fix parameter index in getCount function.
@Talluri, Agreed. However with the current way of testing it is really hard to
see which commit actually broke
This is found by daily BVT run and sent out in daily BVT reporting mail.
It would be great if folks could actually pick up the bugs resulted from
BVT failures immediately.
Thanks,
~Talluri
On 20/02/14 10:20 am, "Sheng Yang" wrote:
>Hi Hugo/Ian,
>
>I suspect https://issues.apache.org/jira/browse
Hi Hugo/Ian,
I suspect https://issues.apache.org/jira/browse/CLOUDSTACK-6130 is caused
by some of recent change of findbugs. It's likely got something wrong with
GeneralDaoBase, and the most recently modifications are:
commit 443acac92792cb2654c3414df276efac404f
Author: Hugo Trippaers
Date: