September 2019 - Infra - Ovirt List Archives

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #353 ovirt-system-tests [poll-upstream-sources]. 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-q660m.

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #353 ovirt-system-tests [poll-upstream-sources]. 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-8qbb1.

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #353 ovirt-system-tests [poll-upstream-sources]. 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-7h4sv.

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #353 ovirt-system-tests [poll-upstream-sources]. 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-mzjfg.

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #353 ovirt-system-tests [poll-upstream-sources]. 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-3tpnk.

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #353 ovirt-system-tests [poll-upstream-sources]. 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-wn6st.

5 years

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 944

by jenkins＠jenkins.phx.ovirt.org

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/944//artifact/exported... Cheers, Jenkins

5 years

1
0
0 / 0

[CQ]: 102717,6 (ovirt-engine) failed "ovirt-master" system tests

by oVirt Jenkins

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

5 years

1
0
0 / 0

[CQ]: 103174, 4 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests, but isn't the failure root cause

by oVirt Jenkins

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

5 years

1
0
0 / 0

[CQ]: 103218,2 (ovirt-vmconsole) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 103218,2 (ovirt-vmconsole) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/103218/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4795/

5 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra September 2019