February 2018 - Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 190 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Feb '18

14 Feb '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/190/ Build Number: 190 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #190 [Dominik Holler] Use ansible to access ovirt-provider-ovn [Sandro Bonazzola] ovirt-dwh: drop fc27 on 4.2 ----------------- Failed Tests: ----------------- No tests ran.

1 1

[CQ]: 87289, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '18

13 Feb '18

A system test invoked by the "ovirt-master" change queue including change 87289,1 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86700,9 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86700,9 (ovirt-engine-api- model) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87289/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86700/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5643/

1 0

[CQ]: 87284, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '18

13 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87284,1 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86692,1 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86692,1 (ovirt-engine-api- model) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87284/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86692/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/779/

1 0

[CQ]: 87489, 7 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 13 Feb '18

13 Feb '18

Change 87489,7 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/87489/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5639/

1 0

[CQ]: 87489,7 (ovirt-engine-metrics) failed "ovirt-4.2" system tests
by oVirt Jenkins 13 Feb '18

13 Feb '18

Change 87489,7 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/87489/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/775/

1 0

[CQ]: 87544, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '18

13 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87544,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87459,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87459,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87544/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87459/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/767/

1 0

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Daniel Belenky (oVirt JIRA) 13 Feb '18

13 Feb '18

This is a multi-part message in MIME format... ------------=_1518516975-15615-100 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-1895: --------------------------------------- It's a known bug that's coming from the Gerrit Trigger Plugin, the current solution is not to push commit message changes if you have CI tests running. > CI votes not forwarded on commit message change > ----------------------------------------------- > > Key: OVIRT-1895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > If a change goes through this flow: > 1. Push an update N > 2. CI triggers check-patch for N > 3. Push another update N+1 that changes only commit message > 4. CI marks +1 N > Then we have logic to not trigger CI for N+1 (with the assumption that > a change to commit message should not affect the result), but also do > not mark +1 N+1, leaving the patch unmarked. > We should either forward the +1, when giving it, to all consecutive > future patchsets that only changed the commit message, or give up on > the optimization and always trigger CI. > As an example, see: > https://gerrit.ovirt.org/87515 > Best regards, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518516975-15615-100 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky commented on OVIRT-1895:</h3> <p>It's a known bug that's coming from the Gerrit Trigger Plugin, the current solution is not to push commit message changes if you have CI tests running.</p> <blockquote><h3>CI votes not forwarded on commit message change</h3> <pre> Key: OVIRT-1895 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra</pre> <p>Hi all, If a change goes through this flow:</p> <ol><li><p>Push an update N</p></li> <li><p>CI triggers check-patch for N</p></li> <li><p>Push another update N+1 that changes only commit message</p></li> <li><p>CI marks +1 N</p></li></ol> <p>Then we have logic to not trigger CI for N+1 (with the assumption that a change to commit message should not affect the result), but also do not mark +1 N+1, leaving the patch unmarked. We should either forward the +1, when giving it, to all consecutive future patchsets that only changed the commit message, or give up on the optimization and always trigger CI. As an example, see: <a href="https://gerrit.ovirt.org/87515">https://gerrit.ovirt.org/87515</a> Best regards, — Didi</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1518516975-15615-100--

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 220 - Failure!
by jenkins＠jenkins.phx.ovirt.org 13 Feb '18

13 Feb '18

------=_Part_203_56058073.1518425929826 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build Number: 220 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #220 [Yuval Turgeman] node-setup: added retries to `ssh nodectl check` ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_203_56058073.1518425929826--

1 1

[CQ]: 42386f6 (ovirt-ansible-cluster-upgrade) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '18

13 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 42386f6 (ovirt-ansible-cluster-upgrade) failed. However, this change seems not to be the root cause for this failure. Change a11d8a2 (ovirt-ansible-cluster-upgrade) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change a11d8a2 (ovirt-ansible-cluster- upgrade) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/42386f62ae2b7… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/a11d8a267cc9e… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/765/

1 0

[CQ]: 87509, 3 (ovirt-engine-metrics) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '18

13 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87509,3 (ovirt-engine-metrics) failed. However, this change seems not to be the root cause for this failure. Change 87454,1 (ovirt-engine-metrics) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87454,1 (ovirt-engine-metrics) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87509/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87454/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/763/

1 0