September 2017 - Infra - oVirt List Archives

[ OST Failure Report ] [ oVirt HE 4.1 ] [ 24.09.17 ] [ set_dc_quota_audit ]
by Gal Ben Haim 24 Sep '17

24 Sep '17

Hi All, In the last days HE 4.1 suite is failing with the following error: *RequestError:* status: 409 reason: Conflict detail: Cannot migrate MACs to another MAC pool, because that action would create duplicates in target MAC pool, which are not allowed. Problematic MACs are 54:52:c0:a8:c 8:63 The MAC above belongs to the HE VM. HE-master works fine. Can you please take a look? *Link to Job:* http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.1/ *Link to all logs*: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.1/42/artif… -- *GAL bEN HAIM* RHV DEVOPS

2 1

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 551 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Sep '17

24 Sep '17

------=_Part_739_168318925.1506265279869 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build Number: 551 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #551 [Daniel Belenky] Add secrets-file binding to std ci [Yuval Turgeman] Adding loop devices to check-merged ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_739_168318925.1506265279869--

1 1

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #810
by jenkins＠jenkins.phx.ovirt.org 24 Sep '17

24 Sep '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ 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_64/…> > 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

1 2

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 381 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Sep '17

24 Sep '17

------=_Part_733_492701593.1506258271779 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build Number: 381 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #381 [Yuval Turgeman] automation: adding loop devices ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_733_492701593.1506258271779--

1 1

[JIRA] (OVIRT-1613) Updates to the ansible suite ( add proper logging )
by eyal edri (oVirt JIRA) 24 Sep '17

24 Sep '17

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.jira.… ] 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.jira.… ]</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> Adding @infra-support to open a ticket. <ol><li>From the console logs the error seems to be:</li></ol> 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? <ol><li>There is a bug in the suite, that when the ansible deploy fails,</li></ol> 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). <ol><li>I recommend adding ‘-vvv’ to the ansible command. Might get more</li></ol> 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: <blockquote>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: <ol><li>boot.log looks good, I see that WildFly 11 is starting</li> <li>server.log also looks good, I see engine was deployed, but it seems to me</li></ol> that it's not complete (like WildFly was killed during engine deployment) <ol><li>engine.log is completely empty – that's very strange, but it's probably</li></ol> 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: <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> _____________________________________________ Infra mailing list Infra(a)ovirt.org <a href="http://lists.ovirt.org/mailman/listinfo/infra">http://lists.ovirt.org/mailman/listinfo/infra</a></blockquote></blockquote> — This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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--

1 0

[JIRA] (OVIRT-1667) jenkins CI fails on findbugs error 137
by eyal edri (oVirt JIRA) 24 Sep '17

24 Sep '17

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.jira.… ] 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/304… > 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.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1667:</h3> [~mwperina] looks like its still failing on findbugs, any thoughts or we need to upgrade the slave memory? <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> Hi, The build <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/304…">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/304…</a> 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: <ol><li>re-trigger the build</li> <li>look into the issue… :-)</li></ol> Thanks, Eitan — IRC: erav</blockquote> — This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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--

1 0

[JIRA] (OVIRT-1667) jenkins CI fails on findbugs error 137
by Eitan Raviv (oVirt JIRA) 24 Sep '17

24 Sep '17

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.jira.… ] 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/304… > 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.jira.… ]</pre> <h3>Eitan Raviv commented on OVIRT-1667:</h3> yes it was rebased <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> Hi, The build <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/304…">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/304…</a> 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: <ol><li>re-trigger the build</li> <li>look into the issue… :-)</li></ol> Thanks, Eitan — IRC: erav</blockquote> — This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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--

1 0

[JIRA] (OVIRT-1667) jenkins CI fails on findbugs error 137
by eyal edri (oVirt JIRA) 24 Sep '17

24 Sep '17

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.jira.… ] 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/304… > 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.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1667:</h3> 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. <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> Hi, The build <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/304…">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/304…</a> 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: <ol><li>re-trigger the build</li> <li>look into the issue… :-)</li></ol> Thanks, Eitan — IRC: erav</blockquote> — This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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--

1 0

[JIRA] (OVIRT-1667) jenkins CI fails on findbugs error 137
by Eitan Raviv (oVirt JIRA) 24 Sep '17

24 Sep '17

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.jira.… ] 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/304… > 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.jira.… ]</pre> <h3>Eitan Raviv commented on OVIRT-1667:</h3> reopening this issue per eyal's comment because the build fails again with same error in same place <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> Hi, The build <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/304…">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/304…</a> 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: <ol><li>re-trigger the build</li> <li>look into the issue… :-)</li></ol> Thanks, Eitan — IRC: erav</blockquote> — This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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--

1 0

[JIRA] (OVIRT-1667) jenkins CI fails on findbugs error 137
by Eitan Raviv (oVirt JIRA) 24 Sep '17

24 Sep '17

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.jira.… ] 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/304… > 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.jira.… ]</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> Hi, The build <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/304…">http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/304…</a> 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: <ol><li>re-trigger the build</li> <li>look into the issue… :-)</li></ol> Thanks, Eitan — IRC: erav</blockquote> — This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100060) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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--

1 0