January 2019 - Infra - oVirt List Archives

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 30 Jan '19

30 Jan '19

Failed to run project_setup.sh for: #3362 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-t6t8j.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 30 Jan '19

30 Jan '19

Failed to run project_setup.sh for: #3360 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-r1fm3.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 30 Jan '19

30 Jan '19

Failed to run project_setup.sh for: #3358 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-d2jzz.

1 0

[CQ]: 5e928a1 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 30 Jan '19

30 Jan '19

Change 5e928a1 (ovirt-ansible-hosted-engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/5e928a1d9… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12590/

1 0

[CQ]: 96815, 29 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Jan '19

30 Jan '19

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

1 0

oVirt infra daily report - unstable production jobs - 720
by jenkins＠jenkins.phx.ovirt.org 30 Jan '19

30 Jan '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/720//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 96464, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jan '19

29 Jan '19

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

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 29 Jan '19

29 Jan '19

Failed to run project_setup.sh for: #3350 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-dg1fx.

1 0

[CQ]: 97353, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jan '19

29 Jan '19

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

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 29 Jan '19

29 Jan '19

Failed to run project_setup.sh for: #2366 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0099.workers-phx.ovirt.org.

1 0