November 2019 - Infra - oVirt List Archives

[CQ]: 103956, 33 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Nov '19

28 Nov '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-engine-ui-extensions_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 28 Nov '19

28 Nov '19

Failed to run project_setup.sh for: #307 ovirt-engine-ui-extensions [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 vm0009.workers-phx.ovirt.org.

1 0

oVirt infra daily report - unstable production jobs - 1022
by jenkins＠jenkins.phx.ovirt.org 28 Nov '19

28 Nov '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/1022//artifact/exported-… Cheers, Jenkins

1 0

[CQ]: 103737, 35 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #6610 ovirt-system-tests [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-integ-tests-container-rdc02.

1 0

[CQ]: 103615, 20 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_gate
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #211. 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-integ-tests-container-mdzhk.

1 0

[CQ]: 103618, 35 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '19

27 Nov '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-engine-ui-extensions_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #306 ovirt-engine-ui-extensions [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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-engine-ui-extensions_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '19

27 Nov '19

Failed to run project_setup.sh for: #304 ovirt-engine-ui-extensions [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 vm0009.workers-phx.ovirt.org.

1 1