November 2017 - Infra - Ovirt List Archives

[CQ]: 83477, 10 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

6 years, 10 months

1
0
0 / 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-snapshot_build-artifacts-el7-x86_64 - Build # 70 - Failure!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_197_1882967440.1510477197099 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-snapshot_build-artif... Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-snapshot_build-artif... Build Number: 70 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #70 [Yuval Turgeman] automation: view install log in console output ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_197_1882967440.1510477197099--

6 years, 10 months

1
1
0 / 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1759: -------------------------------- Description: Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. Here is en example of such an occurance. The following patches were merged in the order specified below: # https://gerrit.ovirt.org/c/83917 # https://gerrit.ovirt.org/c/83918 # https://gerrit.ovirt.org/c/83919 # https://gerrit.ovirt.org/c/83920 The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) This resulted in CQ 'add' command running in the wrong order: # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) We need to come up with a way to make the system properly preserver order. was: Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. Here is en example of such an occurance. The following patches were merged in the order specified below: # https://gerrit.ovirt.org/c/83917 # https://gerrit.ovirt.org/c/83918 # https://gerrit.ovirt.org/c/83919 # https://gerrit.ovirt.org/c/83920 The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) We need to come up with a way to make the system properly preserver order. > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) > # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) > # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) > # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) > This resulted in CQ 'add' command running in the wrong order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1759: -------------------------------- Epic Link: OVIRT-400 > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-1759: ----------------------------------- Summary: Gerrit patches can reach CQ out-of-order Key: OVIRT-1759 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Barak Korren Assignee: infra Priority: High Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. Here is en example of such an occurance. The following patches were merged in the order specified below: # https://gerrit.ovirt.org/c/83917 # https://gerrit.ovirt.org/c/83918 # https://gerrit.ovirt.org/c/83919 # https://gerrit.ovirt.org/c/83920 The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

6 years, 10 months

1
0
0 / 0

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 601 - Failure!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_199_1808796376.1510478321840 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... Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86... Build Number: 601 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #601 [Yuval Turgeman] automation: enable vhost_net and tun ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_199_1808796376.1510478321840--

6 years, 10 months

1
1
0 / 0

[JIRA] (OVIRT-1758) Please add performance-suite to manual job lists

by rgolanbb (oVirt JIRA)

rgolanbb created OVIRT-1758: ------------------------------- Summary: Please add performance-suite to manual job lists Key: OVIRT-1758 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1758 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: rgolanbb Assignee: infra Please add performance-suite-master of suites under http://jenkins.ovirt.org/job/ovirt-system-tests_manual/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

6 years, 10 months

1
0
0 / 0

[CQ]: 83946, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

6 years, 10 months

1
0
0 / 0

[CQ]: 83370, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

6 years, 10 months

1
0
0 / 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 74 - Failure!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_191_21565222.1510466382766 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-... Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-... Build Number: 74 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #74 [Yuval Turgeman] automation: view install log in console output ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_191_21565222.1510466382766--

6 years, 10 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra November 2017