- Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 765
by jenkins＠jenkins.phx.ovirt.org 15 Mar '19

15 Mar '19

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/765//artifact/exported-a… Cheers, Jenkins

1 0

[Ovirt] [CQ weekly status] [15-03-2019]
by Dafna Ron 15 Mar '19

15 Mar '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#1) Last CQ job failure on 4.2 was 14-03-2019 on project v2v-conversion-host due to missing failed build artifacts which was fixed the same day. *CQ-4.3*: RED (#1) Last job to failed today. it had 13 changes and CQ is still bisecting the result. *CQ-Master:* RED (#1) Last failure was today due to a build-artifacts failure. a message was sent to patch owner. Current running jobs for 4.2 [1] and master [2] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

[CQ]: 98057,3 (ovirt-engine-sdk) failed "ovirt-4.3" system tests
by oVirt Jenkins 15 Mar '19

15 Mar '19

Change 98057,3 (ovirt-engine-sdk) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/98057/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/249/

1 0

[CQ]: 97764, 2 (ovirt-engine-api-model) failed "ovirt-master" system tests
by oVirt Jenkins 15 Mar '19

15 Mar '19

Change 97764,2 (ovirt-engine-api-model) 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/97764/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13443/

1 0

[CQ]: 92415, 4 (ovirt-engine-api-metamodel) failed "ovirt-master" system tests
by oVirt Jenkins 15 Mar '19

15 Mar '19

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

1 0

[CQ]: 97764, 2 (ovirt-engine-api-model) failed "ovirt-4.3" system tests
by oVirt Jenkins 15 Mar '19

15 Mar '19

Change 97764,2 (ovirt-engine-api-model) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/97764/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/248/

1 0

[oVirt CI] standard-enqueue - Build #20000 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 15 Mar '19

15 Mar '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/20000/ Build Name: #20000 Build Description: Gerrit: 62940 - ovirt-engine-sdk (3.6, 4.1, 4.2, 4.3, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/62940 - title: sdk: Prepare for next development iteration - project: ovirt-engine-sdk - branch: sdk_3.6 - author: Juan Hernandez <juan.hernandez(a)redhat.com>

1 0

[oVirt CI] standard-enqueue - Build #19993 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 15 Mar '19

15 Mar '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/19993/ Build Name: #19993 Build Description: Gerrit: 62940 - ovirt-engine-sdk (3.6, 4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/62940 - title: sdk: Prepare for next development iteration - project: ovirt-engine-sdk - branch: sdk_3.6 - author: Juan Hernandez <juan.hernandez(a)redhat.com>

1 0

[JIRA] (OVIRT-2697) error before starting tests
by Dafna Ron (oVirt JIRA) 15 Mar '19

15 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2697: ---------------------------------- [~akhiet(a)redhat.com] can we close this ticket? > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2698) Upgrade Suite: Copy from lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to
by Dafna Ron (oVirt JIRA) 15 Mar '19

15 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2698?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2698: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Upgrade Suite: Copy from lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to > -------------------------------------------------------------------------------------- > > Key: OVIRT-2698 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2698 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Liora Milbaum > Assignee: infra > Labels: ost_failures > > [CQ]: 98351, 1 (vdsm-jsonrpc-java) failed "ovirt-4.3" system tests > https://gerrit.ovirt.org/#/c/94713/1 > http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/153/ > [36m # 001_upgrade_engine.test_initialize_engine: [0m[0m[0m > [36m * Copy /home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/upgrade-from-prevrelease-suite-4.3/upgrade-engine-answer-file.conf to lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/answer-file-post: [0m[0m[0m > [36m * Copy /home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/upgrade-from-prevrelease-suite-4.3/upgrade-engine-answer-file.conf to lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/answer-file-post: [32mSuccess[0m (in 0:00:00)[0m > [36m * Collect artifacts: [0m[0m[0m > [36m ~ [Thread-8] Copy from lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to /dev/shm/ost/deployment-upgrade-from-prevrelease-suite-4.3/default/test_logs/001_upgrade_engine.test_initialize_engine-20190307160642/lago-upgrade-from-prevrelease-suite-4-3-engine/_tmp_otopi*: [31mERROR[0m (in 0:00:00)[0m > [36m - [Thread-8] lago-upgrade-from-prevrelease-suite-4-3-engine: [31mERROR[0m (in 0:00:00)[0m > [36m * Collect artifacts: [31mERROR[0m (in 0:00:01)[0m > [36m # 001_upgrade_engine.test_initialize_engine: [31mERROR[0m (in 0:00:49)[0m > [36m # Results located at /dev/shm/ost/deployment-upgrade-from-prevrelease-suite-4.3/001_upgrade_engine.py.junit.xml[0m > [36m@ Run test: 001_upgrade_engine.py: [31mERROR[0m (in 0:00:49)[0m > [31mError occured, aborting > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 383, in do_run > self.cli_plugins[args.ovirtverb].do_run(args) > File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run > self._do_run(**vars(args)) > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 549, in wrapper > return func(*args, **kwargs) > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 560, in wrapper > return func(*args, prefix=prefix, **kwargs) > File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 107, in do_ovirt_runtest > raise RuntimeError('Some tests failed') > RuntimeError: Some tests failed[0m -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0