- Infra - oVirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4471 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Dec '16

12 Dec '16

------=_Part_113_772504385.1481495651180 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4471/, Build Number: 4471, Build Status: FAILURE ------=_Part_113_772504385.1481495651180--

1 1

oVirt infra daily report - unstable production jobs - 165
by jenkins＠jenkins.phx.ovirt.org 12 Dec '16

12 Dec '16

------=_Part_115_940422232.1481497205899 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/165//artifact/exported-a… Cheers, Jenkins ------=_Part_115_940422232.1481497205899 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 11/12/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.0-snapshot_build-artif…">ovirt-appliance_ovirt-4.0-snapshot_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/">ovirt-engine_4.0_upgrade-from-3.6_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-el6-x…">ovirt-guest-agent_master_build-artifacts-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86…">ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_master_build-artifacts-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node_ovirt-3.6_create-iso-el7_merged/">ovirt-node_ovirt-3.6_create-iso-el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-optimizer_4.0_build-artifacts-el6-x86_64/">ovirt-optimizer_4.0_build-artifacts-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/">ovirt_4.0_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.0_check-closure_el7_merged/">repos_4.0_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_115_940422232.1481497205899--

1 0

Re: [ovirt-devel] 4.0.x dependency failure (vdsm-jsonrpc-java)
by Eyal Edri 11 Dec '16

11 Dec '16

Adding infra as well. I see a very strange thing happening on the build artifacts jobs: On [1] we see a successful build of 1.2.10 built in build-artifacts, but on the 2 patches merged after it, its back to 1.2.9 [2]. Is it possible that the 2 patches merged after the version bump weren't rebased on the version branch and were built using older code? I think what we're seeing is a race of 3 patches merged all at the same time ( jenkins shows same datetime on the builds ) and it might be that the 2 builds that show older version run before the version bump was done, even if it shows otherwise on CI. I've run manually the job again and it nows produces 1.2.10 as expected [3], so the job should work once the rpms are deployed ( 30 min ~ ) I believe this is one of the things Zuul will solve, I can't think on something we can do at the moment to prevents such issues, Barak - any ideas? The project has 'fast forward only' mode in Gerrit. [1] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-el7-x86_… [2] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-el7-x86_… [3] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-el7-x86_… On Sun, Dec 11, 2016 at 11:01 AM, Piotr Kliczewski <pkliczew(a)redhat.com> wrote: > Yes, version bump was merged. > > 11 gru 2016 09:57 "Eyal Edri" <eedri(a)redhat.com> napisał(a): > >> Was the version bumped pushed to the repo itself in Gerrit? >> I.e - does build-artifacts builds now the new version 1.2.10? >> >> On Fri, Dec 9, 2016 at 9:33 PM, Sandro Bonazzola <sbonazzo(a)redhat.com> >> wrote: >> >>> >>> >>> Il 09/Dic/2016 18:45, "Piotr Kliczewski" <pkliczew(a)redhat.com> ha >>> scritto: >>> >>> Here [1] is the manual build. We need to check publisher. >>> >>> >>> >>> Manual builds are not published by nightly publisher. Manual builds are >>> meant for releases or for testing. I haven't the laptop with me tonight and >>> tomorrow. Didi, Lev can you handle Sunday morning? >>> >>> >>> >>> >>> Thanks, >>> Piotr >>> >>> [1] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_any_build >>> -artifacts-manual/30/ >>> >>> 9 gru 2016 18:36 "Piotr Kliczewski" <pkliczew(a)redhat.com> napisał(a): >>> >>>> Both us and ds rpms were built. Is it possible to check why new version >>>> was not published to the repo? >>>> >>>> 9 gru 2016 18:07 "Martin Perina" <mperina(a)redhat.com> napisał(a): >>>> >>>>> Piotr, are you able to publish new vdsm-jsonrpc-java 1.2.10 into >>>>> ovirt-4.0-snapshot repo [1]? Or only someone from integration team can do >>>>> that? >>>>> >>>>> Thanks >>>>> >>>>> Martin >>>>> >>>>> [1] http://plain.resources.ovirt.org/pub/ovirt-4.0-snapshot/rpm >>>>> >>>>> >>>>> On Fri, Dec 9, 2016 at 4:54 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: >>>>> >>>>>> See [1]: >>>>>> >>>>>> + yum install --nogpgcheck -y --downloaddir=/dev/shm ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*'*13:55:25* Error: Package: ovirt-engine-backend-4.0.7-0.0.master.20161208233116.git3dff5ce.el7.centos.noarch (alocalsync)*13:55:25* Requires: vdsm-jsonrpc-java >= 1.2.10*13:55:25* Available: vdsm-jsonrpc-java-1.2.9-1.20161208102442.gite5c0c8e.el7.centos.noarch (alocalsync)*13:55:25* vdsm-jsonrpc-java = 1.2.9-1.20161208102442.gite5c0c8e.el7.centos >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> [1] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86… >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Devel mailing list >>>>>> Devel(a)ovirt.org >>>>>> http://lists.phx.ovirt.org/mailman/listinfo/devel >>>>>> >>>>> >>>>> >>> _______________________________________________ >>> Devel mailing list >>> Devel(a)ovirt.org >>> http://lists.phx.ovirt.org/mailman/listinfo/devel >>> >>> >>> >>> _______________________________________________ >>> Devel mailing list >>> Devel(a)ovirt.org >>> http://lists.phx.ovirt.org/mailman/listinfo/devel >>> >> >> >> >> -- >> Eyal Edri >> Associate Manager >> RHV DevOps >> EMEA ENG Virtualization R&D >> Red Hat Israel >> >> phone: +972-9-7692018 >> irc: eedri (on #tlv #rhev-dev #rhev-integ) >> > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

4 7

[JIRA] (OVIRT-932) Wrong Lago version used in CI
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-932?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-932: ----------------------------------------------- Assignee: Gal Ben Haim (was: infra) According to [~bkorren(a)redhat.com] the new changed in mock cache should cause this. Any idea where else it can come from? We cleared the mock cache also on the ovirt-srv22 server, and I now rerun the job to see if it works. > Wrong Lago version used in CI > ----------------------------- > > Key: OVIRT-932 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-932 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Yaniv Kaul > Assignee: Gal Ben Haim > Priority: High > > See http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86… : > Error: package lago-ovirt-0.23.0-1.fc24.noarch requires python-lago-ovirt = 0.23.0, but none of the providers can be installed > It should use v0.28. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-932) Wrong Lago version used in CI
by Yaniv Kaul (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-932?page=com.atlassian.jira.p… ] Yaniv Kaul updated OVIRT-932: ----------------------------- Epic Link: OVIRT-400 > Wrong Lago version used in CI > ----------------------------- > > Key: OVIRT-932 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-932 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Yaniv Kaul > Assignee: infra > Priority: High > > See http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86… : > Error: package lago-ovirt-0.23.0-1.fc24.noarch requires python-lago-ovirt = 0.23.0, but none of the providers can be installed > It should use v0.28. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-932) Wrong Lago version used in CI
by Yaniv Kaul (oVirt JIRA) 11 Dec '16

11 Dec '16

Yaniv Kaul created OVIRT-932: -------------------------------- Summary: Wrong Lago version used in CI Key: OVIRT-932 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-932 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Yaniv Kaul Assignee: infra Priority: High See http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86… : Error: package lago-ovirt-0.23.0-1.fc24.noarch requires python-lago-ovirt = 0.23.0, but none of the providers can be installed It should use v0.28. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

Bug moved to MODIFIED by hook while patches are not all in.
by Yaniv Dary 11 Dec '16

11 Dec '16

Hi, Can you have a look? https://bugzilla.redhat.com/show_bug.cgi?id=827529# This bug moved to MODIFIED by hook while patches are not all in. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary(a)redhat.com IRC : ydary

3 3

Moving NGN system tests to fc24/fc25
by Eyal Edri 11 Dec '16

11 Dec '16

Hi, We're looking to move away from fc23 before it stops working, I see that the ngn system tests still uses it, do we know if it can move to fc24/fc25? I remember el7 wasn't possible when we moved it from fc22. [1] http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_4.0_image-ng… -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-931?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-931: ------------------------------------------------- [~gshinar] thanks for the quick debug, [~ederevea] can we have a list of "problematic hypervisors"? we might want to move them to Lago or production DC. > profile why ovirt-engine check-patch takes between 10-50 min > ------------------------------------------------------------- > > Key: OVIRT-931 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Same job sometimes takes little as 10 min but sometimes high as 50 min. > We need to understand why. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/bui… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
by Gil Shinar (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-931?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-931: ---------------------------------- I have checked two different slaves. One usually takes long 50~ minutes and the other one usually takes 10~ minutes. The one that takes 10~ minutes has 16 cores CPU and the one that takes 50~ minutes has two cores CPU. On top of that, some builds run dao tests and some don't (depend on files that had been changed. > profile why ovirt-engine check-patch takes between 10-50 min > ------------------------------------------------------------- > > Key: OVIRT-931 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Same job sometimes takes little as 10 min but sometimes high as 50 min. > We need to understand why. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/bui… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0