[
https://ovirt-jira.atlassian.net/browse/OVIRT-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=18303#comment-18303
]
Juan Hernández commented on OVIRT-624:
--
This is the patch that introduced the issue:
restapi: Always
On 07/08/2016 10:12 AM, Eyal Edri wrote:
> So I'm not sure its a false positive, it was real issue at that time and
> a rebase was needed to fix it.
> What we do need to investigate is why juan's patch wasn't given -1
> before merge, juan - can you check what did the findbugs job say on your
>
So I'm not sure its a false positive, it was real issue at that time and a
rebase was needed to fix it.
What we do need to investigate is why juan's patch wasn't given -1 before
merge, juan - can you check what did the findbugs job say on your patch?
On Fri, Jul 8, 2016 at 11:08 AM, Juan
[
https://ovirt-jira.atlassian.net/browse/OVIRT-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=18301#comment-18301
]
Juan Hernández commented on OVIRT-624:
--
Eyal, that findbugs failure was introduced by a patch of mine,
On 07/08/2016 09:29 AM, Eyal Edri wrote:
> I marked this build as keep forever so we can debug it.
> Also, we are in the process of moving to a new findbugs jobs which are
> written in Yaml and have a few small fixes,
> so i've disabled the old job in favor
> of
[
https://ovirt-jira.atlassian.net/browse/OVIRT-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=18300#comment-18300
]
eyal edri [Administrator] commented on OVIRT-624:
-
I marked this build as keep forever so we
I marked this build as keep forever so we can debug it.
Also, we are in the process of moving to a new findbugs jobs which are
written in Yaml and have a few small fixes,
so i've disabled the old job in favor of
http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_created_test/.
@snaftaly
Martin Mucha created OVIRT-624:
--
Summary: another invalid CI-1
Key: OVIRT-624
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-624
Project: oVirt - virtualization made easy
Issue Type:
