[ https://ovirt-jira.atlassian.net/browse/OVIRT-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34900#comment-34900 ] eyal edri commented on OVIRT-1644: ---------------------------------- After talking with [~danken@redhat.com] and [~mureinik] we agreed there is actually no need to run findbugs more than once (i.e both on fedora and el7) , as its JAVA code, and os independent. So we'll try to use the new feature from CI to use ENV variables in check-patch.sh to make sure we only run it once on el7, thanks for [~mureinik] for looking into it!

very common false failure of ovirt-engine_master_check-patch-fc25-x86_64 ------------------------------------------------------------------------

Key: OVIRT-1644 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1644 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra

Like many many other executions of the said job, http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc25-x86_64/137... fails with [INFO] UICommonWeb ........................................ FAILURE [02:26 min] ... [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli) on project uicommonweb: Execution default-cli of goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java returned: 137 -> [Help 1] which according to https://github.com/travis-ci/travis-ci/issues/4488 may be sue to lack of memory. Please look into it; having people blindly retrigger failed jobs is bad education.

-- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)