This is a multi-part message in MIME format... ------------=_1505226239-28082-401 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34896#comment-34896 ] Greg Sheremeta commented on OVIRT-1644: --------------------------------------- Actually, this isn't our typical GWT build death. That one occurs when building the webadmin project, and this occurred two projects sooner, uicommonweb. I actually saw this failure on one of my patches the other day, and I wondered what it was. A simple rerun fixed it. It does appear that this findbugs needs more memory. Can we test that?
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) ------------=_1505226239-28082-401 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1644?page=com.atlassian.jira.p... ]</pre> <h3>Greg Sheremeta commented on OVIRT-1644:</h3> <p>Actually, this isn't our typical GWT build death. That one occurs when building the webadmin project, and this occurred two projects sooner, uicommonweb.</p> <p>I actually saw this failure on one of my patches the other day, and I wondered what it was. A simple rerun fixed it.</p> <p>It does appear that this findbugs needs more memory. Can we test that?</p> <blockquote><h3>very common false failure of ovirt-engine_master_check-patch-fc25-x86_64</h3> <pre> 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</pre> <p>Like many many other executions of the said job, <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc25-x86_64/13784/">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc25-x86_64/13784/</a> 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 <a href="https://github.com/travis-ci/travis-ci/issues/4488">https://github.com/travis-ci/travis-ci/issues/4488</a> may be sue to lack of memory. Please look into it; having people blindly retrigger failed jobs is bad education.</p></blockquote> <p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyzY..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1505226239-28082-401--