January 2018 - Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 150 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Jan '18

14 Jan '18

------=_Part_70_1033959891.1515812549553 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/150/ Build Number: 150 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #150 [Gal Ben Haim] master: Add host's image to the internal_repo [Nir Soffer] vdsm: Disable Fedora 26 builds on master ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_70_1033959891.1515812549553--

1 2

[JIRA] (OVIRT-1844) jenkins_master_deploy-configs_merged failing do to missing libraries
by eyal edri (oVirt JIRA) 14 Jan '18

14 Jan '18

This is a multi-part message in MIME format... ------------=_1515916522-21230-200 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1844?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1844: ---------------------------------- Should we also add it to the global_setup script to be installed? > jenkins_master_deploy-configs_merged failing do to missing libraries > -------------------------------------------------------------------- > > Key: OVIRT-1844 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1844 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > Since patches related to OVIRT-1746, mainly https://gerrit.ovirt.org/85158/, got merged, jenkins configs are no longer deployed since libraries required by usrc.py are missing on the Jenkins: > http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso… > File "/var/lib/data/jenkins/jobs/jenkins_master_deploy-configs_merged/workspace/jenkins/scripts/usrc.py", line 13, in <module> > from xdg.BaseDirectory import xdg_cache_home > ImportError: No module named xdg.BaseDirectory -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515916522-21230-200 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1844?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1844:</h3> <p>Should we also add it to the global_setup script to be installed?</p> <blockquote><h3>jenkins_master_deploy-configs_merged failing do to missing libraries</h3> <pre> Key: OVIRT-1844 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1844 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: High</pre> <p>Since patches related to OVIRT-1746, mainly <a href="https://gerrit.ovirt.org/85158/">https://gerrit.ovirt.org/85158/</a>, got merged, jenkins configs are no longer deployed since libraries required by usrc.py are missing on the Jenkins: <a href="http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso…">http://jenkins.ovirt.org/job/jenkins_master_deploy-configs_merged/997/conso…</a></p> <pre> File "/var/lib/data/jenkins/jobs/jenkins_master_deploy-configs_merged/workspace/jenkins/scripts/usrc.py", line 13, in <module> from xdg.BaseDirectory import xdg_cache_home ImportError: No module named xdg.BaseDirectory</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</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> ------------=_1515916522-21230-200--

1 0

[CQ]: 86087, 7 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-master" change queue including change 86087,7 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 85996,6 (vdsm) 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 85996,6 (vdsm) 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/86087/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85996/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4797/

1 0

[JIRA] (OVIRT-1845) Removing build jobs makes change-queue fail with an exception
by Barak Korren (oVirt JIRA) 14 Jan '18

14 Jan '18

This is a multi-part message in MIME format... ------------=_1515912445-32493-213 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1845?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1845: -------------------------------- Assignee: Barak Korren (was: infra) Status: In Progress (was: To Do) > Removing build jobs makes change-queue fail with an exception > -------------------------------------------------------------- > > Key: OVIRT-1845 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1845 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > When changes are added to the change queue, it records the build jobs that build artifacts for changed code. > If the build jobs are removed between the time the change is added to the queue and the time a tested jobs including that change is started, the code checking for completion of the build jobs would fail with an exception looking like the following: > {code} > java.lang.NullPointerException: Cannot invoke method getBuild() on null object > at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) > at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:35) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) > at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:52) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) > at Script1$_all_builds_done_closure4.doCall(Script1.groovy:265) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) > at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) > at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294) > at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) > {code} > '{{Script1}}' in this stack trace refers to our '{{change-queue-tester.groovy}}' script. Relevant code section is the following: > {code} > @NonCPS > def all_builds_done(builds) { > return !builds.any { > if(Jenkins.instance.getItem(it.job_name).getBuild(it.build_id).isBuilding()) { > print("${it.job_name} (${it.build_id}) still building") > return true > } > return false > } > } > {code} > The issue it with not checking for '{{null}}' return from the '{{Jenkins.instance.getItem(it.job_name)}}' funcntion call. > We should probably check for '{{null}}' there and just ignore it. Similar check will probably be needed in other places in the code like for example when composing the '{{extra-sources}}' file from the build job URLs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515912445-32493-213 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1845?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1845:</h3> <pre>Assignee: Barak Korren (was: infra) Status: In Progress (was: To Do)</pre> <blockquote><h3>Removing build jobs makes change-queue fail with an exception</h3> <pre> Key: OVIRT-1845 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1845 Project: oVirt - virtualization made easy Issue Type: Bug Components: Change Queue Reporter: Barak Korren Assignee: Barak Korren Priority: Highest</pre> <p>When changes are added to the change queue, it records the build jobs that build artifacts for changed code. If the build jobs are removed between the time the change is added to the queue and the time a tested jobs including that change is started, the code checking for completion of the build jobs would fail with an exception looking like the following: {code} java.lang.NullPointerException: Cannot invoke method getBuild() on null object</p> <pre>at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:35) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:52) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) at Script1$_all_builds_done_closure4.doCall(Script1.groovy:265) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)</pre> <p>{code} ‘{{Script1}}’ in this stack trace refers to our ‘{{change-queue-tester.groovy}}’ script. Relevant code section is the following: {code} @NonCPS def all_builds_done(builds) {</p> <pre> return !builds.any { if(Jenkins.instance.getItem(it.job_name).getBuild(it.build_id).isBuilding()) { print("${it.job_name} (${it.build_id}) still building") return true } return false }</pre> <p>} {code} The issue it with not checking for ‘{{null}}’ return from the ‘{{Jenkins.instance.getItem(it.job_name)}}’ funcntion call. We should probably check for ‘{{null}}’ there and just ignore it. Similar check will probably be needed in other places in the code like for example when composing the ‘{{extra-sources}}’ file from the build job URLs.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</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> ------------=_1515912445-32493-213--

1 0

[JIRA] (OVIRT-1845) Removing build jobs makes change-queue fail with an exception
by Barak Korren (oVirt JIRA) 14 Jan '18

14 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1845?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1845: -------------------------------- Epic Link: OVIRT-400 > Removing build jobs makes change-queue fail with an exception > -------------------------------------------------------------- > > Key: OVIRT-1845 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1845 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > When changes are added to the change queue, it records the build jobs that build artifacts for changed code. > If the build jobs are removed between the time the change is added to the queue and the time a tested jobs including that change is started, the code checking for completion of the build jobs would fail with an exception looking like the following: > {code} > java.lang.NullPointerException: Cannot invoke method getBuild() on null object > at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91) > at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) > at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:35) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) > at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:52) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) > at Script1$_all_builds_done_closure4.doCall(Script1.groovy:265) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) > at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) > at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294) > at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) > {code} > '{{Script1}}' in this stack trace refers to our '{{change-queue-tester.groovy}}' script. Relevant code section is the following: > {code} > @NonCPS > def all_builds_done(builds) { > return !builds.any { > if(Jenkins.instance.getItem(it.job_name).getBuild(it.build_id).isBuilding()) { > print("${it.job_name} (${it.build_id}) still building") > return true > } > return false > } > } > {code} > The issue it with not checking for '{{null}}' return from the '{{Jenkins.instance.getItem(it.job_name)}}' funcntion call. > We should probably check for '{{null}}' there and just ignore it. Similar check will probably be needed in other places in the code like for example when composing the '{{extra-sources}}' file from the build job URLs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1845) Removing build jobs makes change-queue fail with an exception
by Barak Korren (oVirt JIRA) 14 Jan '18

14 Jan '18

This is a multi-part message in MIME format... ------------=_1515912385-18534-219 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1845: ----------------------------------- Summary: Removing build jobs makes change-queue fail with an exception Key: OVIRT-1845 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1845 Project: oVirt - virtualization made easy Issue Type: Bug Components: Change Queue Reporter: Barak Korren Assignee: infra Priority: Highest When changes are added to the change queue, it records the build jobs that build artifacts for changed code. If the build jobs are removed between the time the change is added to the queue and the time a tested jobs including that change is started, the code checking for completion of the build jobs would fail with an exception looking like the following: {code} java.lang.NullPointerException: Cannot invoke method getBuild() on null object at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:35) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:52) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) at Script1$_all_builds_done_closure4.doCall(Script1.groovy:265) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) {code} '{{Script1}}' in this stack trace refers to our '{{change-queue-tester.groovy}}' script. Relevant code section is the following: {code} @NonCPS def all_builds_done(builds) { return !builds.any { if(Jenkins.instance.getItem(it.job_name).getBuild(it.build_id).isBuilding()) { print("${it.job_name} (${it.build_id}) still building") return true } return false } } {code} The issue it with not checking for '{{null}}' return from the '{{Jenkins.instance.getItem(it.job_name)}}' funcntion call. We should probably check for '{{null}}' there and just ignore it. Similar check will probably be needed in other places in the code like for example when composing the '{{extra-sources}}' file from the build job URLs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515912385-18534-219 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1845:</h3> <pre> Summary: Removing build jobs makes change-queue fail with an exception Key: OVIRT-1845 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1845 Project: oVirt - virtualization made easy Issue Type: Bug Components: Change Queue Reporter: Barak Korren Assignee: infra Priority: Highest</pre> <p>When changes are added to the change queue, it records the build jobs that build artifacts for changed code.</p> <p>If the build jobs are removed between the time the change is added to the queue and the time a tested jobs including that change is started, the code checking for completion of the build jobs would fail with an exception looking like the following:</p> <p>{code} java.lang.NullPointerException: Cannot invoke method getBuild() on null object</p> <pre>at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:35) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:52) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) at Script1$_all_builds_done_closure4.doCall(Script1.groovy:265) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)</pre> <p>{code}</p> <p>‘{{Script1}}’ in this stack trace refers to our ‘{{change-queue-tester.groovy}}’ script. Relevant code section is the following:</p> <p>{code} @NonCPS def all_builds_done(builds) {</p> <pre> return !builds.any { if(Jenkins.instance.getItem(it.job_name).getBuild(it.build_id).isBuilding()) { print("${it.job_name} (${it.build_id}) still building") return true } return false }</pre> <p>} {code}</p> <p>The issue it with not checking for ‘{{null}}’ return from the ‘{{Jenkins.instance.getItem(it.job_name)}}’ funcntion call.</p> <p>We should probably check for ‘{{null}}’ there and just ignore it. Similar check will probably be needed in other places in the code like for example when composing the ‘{{extra-sources}}’ file from the build job URLs.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</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> ------------=_1515912385-18534-219--

1 0

[CQ]: 85958, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-master" change queue including change 85958,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 85996,6 (vdsm) 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 85996,6 (vdsm) 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/85958/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85996/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4790/

1 0

[CQ]: 85996,6 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '18

14 Jan '18

Change 85996,6 (vdsm) 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/85996/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4783/

1 0

[CQ]: 86122,4 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '18

14 Jan '18

Change 86122,4 (ovirt-engine) 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/86122/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4776/

1 0

[CQ]: 84997, 44 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-master" change queue including change 84997,44 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 84331,15 (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 84331,15 (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/84997/44 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/84331/15 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4769/

1 0