Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #810
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_6...>
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_6...>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
> git --version # timeout=10
> git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/13/75913/5:patch --prune
> git rev-parse origin/patch^{commit} # timeout=10
> git rev-parse patch^{commit} # timeout=10
Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch)
Commit message: "Exclude big packages from mirrors"
> git config core.sparsecheckout # timeout=10
> git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f
> git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10
[system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins7619917700882309602.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
File "/usr/bin/reposync", line 343, in <module>
main()
File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup
return self._getRepos(thisrepo, True)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos
self._repos.doSetup(thisrepo)
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1478, in _commonLoadRepoXML
self._revertOldRepoXML()
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1323, in _revertOldRepoXML
os.rename(old_data['old_local'], old_data['local'])
OSError: [Errno 2] No such file or directory
Build step 'Execute shell' marked build as failure
7 years, 2 months
[JIRA] (OVIRT-1613) Updates to the ansible suite ( add proper logging )
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1506252065-10815-416
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=com.atlassian.jir... ]
eyal edri updated OVIRT-1613:
-----------------------------
Resolution: Fixed
Status: Done (was: To Do)
> Updates to the ansible suite ( add proper logging )
> ---------------------------------------------------
>
> Key: OVIRT-1613
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1613
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Nadav Goldin
> Assignee: Ondra Machacek
>
> Adding @infra-support to open a ticket.
> 1. From the console logs the error seems to be:
> 02:50:07 TASK [ovirt-deploy : Import template from glance]
> ******************************
> 02:50:12 An exception occurred during task execution. To see the full
> traceback, use -vvv. The error was: AttributeError: 'TemplatesModule'
> object has no attribute 'wait_for_import'
> 02:50:12 fatal: [lago-ansible-suite-master-engine]: FAILED! =>
> {"changed": false, "failed": true, "msg": "'TemplatesModule' object
> has no attribute 'wait_for_import'"}
> 02:50:12 to retry, use: --limit
> @/home/jenkins/workspace/ovirt-system-tests_ansible-suite-master/ovirt-system-tests/ansible-suite-master/engine.retry
> Maybe something changed recently in the Ansible roles?
> 2. There is a bug in the suite, that when the ansible deploy fails,
> the logs are not collected. That is why you see no logs(the logs you
> see are right after 'initialize_engine', and not after the ansible
> failure).
> 3. I recommend adding '-vvv' to the ansible command. Might get more
> verbose logs, but easier to debug next time.
> Thanks,
> Nadav.
> On Thu, Aug 24, 2017 at 9:49 AM, Martin Perina <mperina(a)redhat.com> wrote:
> > Hi,
> >
> > Ansible test suite is failing for a few days, Lago says that it's failing on
> > engine initialization. I've been looking on the logs, but I was unable to
> > find any error. But there's something strange in wildfly logs on engine:
> >
> > 1. boot.log looks good, I see that WildFly 11 is starting
> > 2. server.log also looks good, I see engine was deployed, but it seems to me
> > that it's not complete (like WildFly was killed during engine deployment)
> > 3. engine.log is completely empty - that's very strange, but it's probably
> > related to my suspicion above
> >
> > In lago logs I can see that ovirt-engine service is being started, but no
> > info about being killed/stop.
> >
> > Any idea what could have happened?
> >
> > Thanks a lot
> >
> > Martin
> >
> >
> > On Thu, Aug 24, 2017 at 4:50 AM, <jenkins(a)jenkins.phx.ovirt.org> wrote:
> >>
> >> Project:
> >> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/
> >> Build:
> >> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/7/
> >> Build Number: 7
> >> Build Status: Still Failing
> >> Triggered By: Started by timer
> >>
> >> -------------------------------------
> >> Changes Since Last Success:
> >> -------------------------------------
> >> Changes for Build #5
> >> [Eyal Shenitzky] basic-suite-master: add cold_storage_migration test
> >>
> >> [Barak Korren] Adapting OST manual job to macro changes
> >>
> >> [Daniel Belenky] Add support for secrets and credentials to STD CI
> >>
> >>
> >> Changes for Build #6
> >> No changes
> >>
> >> Changes for Build #7
> >> [Your Name] Use a long name with special chars as a network name
> >>
> >> [Barak Korren] Fix small bug in slave repo setup
> >>
> >> [Daniel Belenky] mock_runner fix empty mrmap bug
> >>
> >>
> >>
> >>
> >> -----------------
> >> Failed Tests:
> >> -----------------
> >> All tests passed
> >
> >
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100060)
------------=_1506252065-10815-416
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=com.atlassian.jir... ]</pre>
<h3>eyal edri updated OVIRT-1613:</h3>
<pre>Resolution: Fixed
Status: Done (was: To Do)</pre>
<blockquote><h3>Updates to the ansible suite ( add proper logging )</h3>
<pre> Key: OVIRT-1613
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1613
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Nadav Goldin
Assignee: Ondra Machacek</pre>
<p>Adding @infra-support to open a ticket.</p>
<ol><li><p>From the console logs the error seems to be:</p></li></ol>
<p>02:50:07 TASK [ovirt-deploy : Import template from glance] <strong>***************************</strong>* 02:50:12 An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeError: ‘TemplatesModule’ object has no attribute ‘wait_for_import’ 02:50:12 fatal: [lago-ansible-suite-master-engine]: FAILED! => {"changed": false, “failed”: true, “msg”: “'TemplatesModule' object has no attribute 'wait_for_import'”} 02:50:12 to retry, use: --limit @/home/jenkins/workspace/ovirt-system-tests_ansible-suite-master/ovirt-system-tests/ansible-suite-master/engine.retry Maybe something changed recently in the Ansible roles?</p>
<ol><li><p>There is a bug in the suite, that when the ansible deploy fails,</p></li></ol>
<p>the logs are not collected. That is why you see no logs(the logs you see are right after ‘initialize_engine’, and not after the ansible failure).</p>
<ol><li><p>I recommend adding ‘-vvv’ to the ansible command. Might get more</p></li></ol>
<p>verbose logs, but easier to debug next time. Thanks, Nadav. On Thu, Aug 24, 2017 at 9:49 AM, Martin Perina <mperina(a)redhat.com> wrote:</p>
<blockquote><p>Hi,</p>
<p>Ansible test suite is failing for a few days, Lago says that it's failing on engine initialization. I've been looking on the logs, but I was unable to find any error. But there's something strange in wildfly logs on engine:</p>
<ol><li><p>boot.log looks good, I see that WildFly 11 is starting</p></li>
<li><p>server.log also looks good, I see engine was deployed, but it seems to me</p></li></ol>
<p>that it's not complete (like WildFly was killed during engine deployment)</p>
<ol><li><p>engine.log is completely empty – that's very strange, but it's probably</p></li></ol>
<p>related to my suspicion above</p>
<p>In lago logs I can see that ovirt-engine service is being started, but no info about being killed/stop.</p>
<p>Any idea what could have happened?</p>
<p>Thanks a lot</p>
<p>Martin</p>
<p>On Thu, Aug 24, 2017 at 4:50 AM, <jenkins(a)jenkins.phx.ovirt.org> wrote:</p>
<blockquote><pre>Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/7/
Build Number: 7
Build Status: Still Failing
Triggered By: Started by timer</pre>
<pre>-------------------------------------
Changes Since Last Success:
-------------------------------------
Changes for Build #5
[Eyal Shenitzky] basic-suite-master: add cold_storage_migration test</pre>
<pre>[Barak Korren] Adapting OST manual job to macro changes</pre>
<pre>[Daniel Belenky] Add support for secrets and credentials to STD CI</pre>
<pre>Changes for Build #6
No changes</pre>
<pre>Changes for Build #7
[Your Name] Use a long name with special chars as a network name</pre>
<pre>[Barak Korren] Fix small bug in slave repo setup</pre>
<pre>[Daniel Belenky] mock_runner fix empty mrmap bug</pre>
<pre>-----------------
Failed Tests:
-----------------
All tests passed</pre></blockquote>
<p><em>____________________________________________</em>_ Infra mailing list Infra(a)ovirt.org <a href="http://lists.ovirt.org/mailman/listinfo/infra">http://lists.ovirt.org/mailman/listinfo/infra</a></p></blockquote></blockquote>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." 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>
------------=_1506252065-10815-416--
7 years, 2 months
[JIRA] (OVIRT-1667) jenkins CI fails on findbugs error 137
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1506247856-28057-441
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1667?page=com.atlassian.jir... ]
eyal edri commented on OVIRT-1667:
----------------------------------
[~mwperina] looks like its still failing on findbugs, any thoughts or we need to upgrade the slave memory?
> jenkins CI fails on findbugs error 137
> --------------------------------------
>
> Key: OVIRT-1667
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1667
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Eitan Raviv
> Assignee: infra
>
> Hi,
> The build
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...
> failed with the following error:
> *05:03:18* [ERROR] Failed to execute goal
> org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli)
> on project webadmin: Execution default-cli of goal
> org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java
> returned: 137 -> [Help 1]
> After some googling it looks like this might be an out of memory error of
> the process. I understand from Alona that this is a know issue.
> Could you please:
> 1. re-trigger the build
> 2. look into the issue... :-)
> Thanks,
> Eitan
> --
> IRC: erav
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100060)
------------=_1506247856-28057-441
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1667?page=com.atlassian.jir... ]</pre>
<h3>eyal edri commented on OVIRT-1667:</h3>
<p>[~mwperina] looks like its still failing on findbugs, any thoughts or we need to upgrade the slave memory?</p>
<blockquote><h3>jenkins CI fails on findbugs error 137</h3>
<pre> Key: OVIRT-1667
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1667
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Eitan Raviv
Assignee: infra</pre>
<p>Hi, The build <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...</a> failed with the following error: <strong>05:03:18</strong> [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli) on project webadmin: Execution default-cli of goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java returned: 137 -> [Help 1] After some googling it looks like this might be an out of memory error of the process. I understand from Alona that this is a know issue. Could you please:</p>
<ol><li><p>re-trigger the build</p></li>
<li><p>look into the issue… <span class="smiley-happy">:-)</span></p></li></ol>
<p>Thanks, Eitan — IRC: erav</p></blockquote>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." 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>
------------=_1506247856-28057-441--
7 years, 2 months
[JIRA] (OVIRT-1667) jenkins CI fails on findbugs error 137
by Eitan Raviv (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1506246574-15876-404
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1667?page=com.atlassian.jir... ]
Eitan Raviv commented on OVIRT-1667:
------------------------------------
yes it was rebased
> jenkins CI fails on findbugs error 137
> --------------------------------------
>
> Key: OVIRT-1667
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1667
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Eitan Raviv
> Assignee: infra
>
> Hi,
> The build
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...
> failed with the following error:
> *05:03:18* [ERROR] Failed to execute goal
> org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli)
> on project webadmin: Execution default-cli of goal
> org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java
> returned: 137 -> [Help 1]
> After some googling it looks like this might be an out of memory error of
> the process. I understand from Alona that this is a know issue.
> Could you please:
> 1. re-trigger the build
> 2. look into the issue... :-)
> Thanks,
> Eitan
> --
> IRC: erav
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100060)
------------=_1506246574-15876-404
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1667?page=com.atlassian.jir... ]</pre>
<h3>Eitan Raviv commented on OVIRT-1667:</h3>
<p>yes it was rebased</p>
<blockquote><h3>jenkins CI fails on findbugs error 137</h3>
<pre> Key: OVIRT-1667
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1667
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Eitan Raviv
Assignee: infra</pre>
<p>Hi, The build <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...</a> failed with the following error: <strong>05:03:18</strong> [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli) on project webadmin: Execution default-cli of goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java returned: 137 -> [Help 1] After some googling it looks like this might be an out of memory error of the process. I understand from Alona that this is a know issue. Could you please:</p>
<ol><li><p>re-trigger the build</p></li>
<li><p>look into the issue… <span class="smiley-happy">:-)</span></p></li></ol>
<p>Thanks, Eitan — IRC: erav</p></blockquote>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." 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>
------------=_1506246574-15876-404--
7 years, 2 months
[JIRA] (OVIRT-1667) jenkins CI fails on findbugs error 137
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1506246514-16630-326
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1667?page=com.atlassian.jir... ]
eyal edri commented on OVIRT-1667:
----------------------------------
was the patch rebased on latest master? to make sure the fixed are included?
In any case, I re-triggered it after rebasing, lets see how it goes.
> jenkins CI fails on findbugs error 137
> --------------------------------------
>
> Key: OVIRT-1667
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1667
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Eitan Raviv
> Assignee: infra
>
> Hi,
> The build
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...
> failed with the following error:
> *05:03:18* [ERROR] Failed to execute goal
> org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli)
> on project webadmin: Execution default-cli of goal
> org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java
> returned: 137 -> [Help 1]
> After some googling it looks like this might be an out of memory error of
> the process. I understand from Alona that this is a know issue.
> Could you please:
> 1. re-trigger the build
> 2. look into the issue... :-)
> Thanks,
> Eitan
> --
> IRC: erav
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100060)
------------=_1506246514-16630-326
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1667?page=com.atlassian.jir... ]</pre>
<h3>eyal edri commented on OVIRT-1667:</h3>
<p>was the patch rebased on latest master? to make sure the fixed are included? In any case, I re-triggered it after rebasing, lets see how it goes.</p>
<blockquote><h3>jenkins CI fails on findbugs error 137</h3>
<pre> Key: OVIRT-1667
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1667
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Eitan Raviv
Assignee: infra</pre>
<p>Hi, The build <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...</a> failed with the following error: <strong>05:03:18</strong> [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli) on project webadmin: Execution default-cli of goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java returned: 137 -> [Help 1] After some googling it looks like this might be an out of memory error of the process. I understand from Alona that this is a know issue. Could you please:</p>
<ol><li><p>re-trigger the build</p></li>
<li><p>look into the issue… <span class="smiley-happy">:-)</span></p></li></ol>
<p>Thanks, Eitan — IRC: erav</p></blockquote>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." 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>
------------=_1506246514-16630-326--
7 years, 2 months
[JIRA] (OVIRT-1667) jenkins CI fails on findbugs error 137
by Eitan Raviv (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1506246165-26040-365
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1667?page=com.atlassian.jir... ]
Eitan Raviv commented on OVIRT-1667:
------------------------------------
reopening this issue per eyal's comment because the build fails again with same error in same place
> jenkins CI fails on findbugs error 137
> --------------------------------------
>
> Key: OVIRT-1667
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1667
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Eitan Raviv
> Assignee: infra
>
> Hi,
> The build
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...
> failed with the following error:
> *05:03:18* [ERROR] Failed to execute goal
> org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli)
> on project webadmin: Execution default-cli of goal
> org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java
> returned: 137 -> [Help 1]
> After some googling it looks like this might be an out of memory error of
> the process. I understand from Alona that this is a know issue.
> Could you please:
> 1. re-trigger the build
> 2. look into the issue... :-)
> Thanks,
> Eitan
> --
> IRC: erav
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100060)
------------=_1506246165-26040-365
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1667?page=com.atlassian.jir... ]</pre>
<h3>Eitan Raviv commented on OVIRT-1667:</h3>
<p>reopening this issue per eyal's comment because the build fails again with same error in same place</p>
<blockquote><h3>jenkins CI fails on findbugs error 137</h3>
<pre> Key: OVIRT-1667
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1667
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Eitan Raviv
Assignee: infra</pre>
<p>Hi, The build <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...</a> failed with the following error: <strong>05:03:18</strong> [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli) on project webadmin: Execution default-cli of goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java returned: 137 -> [Help 1] After some googling it looks like this might be an out of memory error of the process. I understand from Alona that this is a know issue. Could you please:</p>
<ol><li><p>re-trigger the build</p></li>
<li><p>look into the issue… <span class="smiley-happy">:-)</span></p></li></ol>
<p>Thanks, Eitan — IRC: erav</p></blockquote>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." 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>
------------=_1506246165-26040-365--
7 years, 2 months
[JIRA] (OVIRT-1667) jenkins CI fails on findbugs error 137
by Eitan Raviv (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1506246104-30650-304
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1667?page=com.atlassian.jir... ]
Eitan Raviv reopened OVIRT-1667:
--------------------------------
> jenkins CI fails on findbugs error 137
> --------------------------------------
>
> Key: OVIRT-1667
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1667
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Eitan Raviv
> Assignee: infra
>
> Hi,
> The build
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...
> failed with the following error:
> *05:03:18* [ERROR] Failed to execute goal
> org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli)
> on project webadmin: Execution default-cli of goal
> org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java
> returned: 137 -> [Help 1]
> After some googling it looks like this might be an out of memory error of
> the process. I understand from Alona that this is a know issue.
> Could you please:
> 1. re-trigger the build
> 2. look into the issue... :-)
> Thanks,
> Eitan
> --
> IRC: erav
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100060)
------------=_1506246104-30650-304
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1667?page=com.atlassian.jir... ]</pre>
<h3>Eitan Raviv reopened OVIRT-1667:</h3>
<blockquote><h3>jenkins CI fails on findbugs error 137</h3>
<pre> Key: OVIRT-1667
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1667
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Eitan Raviv
Assignee: infra</pre>
<p>Hi, The build <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/3...</a> failed with the following error: <strong>05:03:18</strong> [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli) on project webadmin: Execution default-cli of goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java returned: 137 -> [Help 1] After some googling it looks like this might be an out of memory error of the process. I understand from Alona that this is a know issue. Could you please:</p>
<ol><li><p>re-trigger the build</p></li>
<li><p>look into the issue… <span class="smiley-happy">:-)</span></p></li></ol>
<p>Thanks, Eitan — IRC: erav</p></blockquote>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYL..." 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>
------------=_1506246104-30650-304--
7 years, 2 months
