[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5466 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

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #155

See -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #13 vdsm [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

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #13 vdsm [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

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #13 vdsm [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

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources

Failed to run project_setup.sh for: #13 vdsm [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

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 190 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/190/ Build Number: 190 Build Status: Still Failing Triggered By: Started by timer - Changes

[CQ]: 103148,6 (vdsm) failed "ovirt-master" system tests

Change 103148,6 (vdsm) 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

oVirt infra daily report - unstable production jobs - 944

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-artifacts/upstream_report.html Cheers, Jenkins

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

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

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #154

See Changes: [Barak Korren] gate: Enable gating of ST project [Barak Korren] staging gate job: use dummy ST project -- Started by timer

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

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

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

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

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

A system test invoked by the "ovirt-4.2" change queue including change 103224,3 (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

[CQ]: 102848,9 (vdsm) failed "ovirt-master" system tests

Change 102848,9 (vdsm) 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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #604 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #604 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5465 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5465 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

[CQ]: b7351eb (ovirt-web-ui) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change b7351eb (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 66bcd08 (ovirt-web-ui) that this change depends on or is based on, was detected as the cause of the testing failures.

[JENKINS] Failed to setup proejct jenkins_gate

Failed to run project_setup.sh for: #97. 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

[JENKINS] Failed to setup proejct jenkins_gate

Failed to run project_setup.sh for: #96. 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

[CQ]: e052308 (ovirt-web-ui) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change e052308 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 66bcd08 (ovirt-web-ui) that this change depends on or is based on, was detected as the cause of the testing failures.

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5464 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5463 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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #701 vdsm [check-network]. 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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #701 vdsm [check-network]. 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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #701 vdsm [check-network]. 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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #701 vdsm [check-network]. 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

[JIRA] (OVIRT-2792) Error running global_setup.sh with metrics suite

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin updated OVIRT-2792: Issue Type: Bug (was: By-EMAIL) > Error running global_setup.sh with metrics

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5462 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5462 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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #602 kubernetes-nmstate [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

[JIRA] (OVIRT-2792) Error running global_setup.sh with metrics suite

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Marchukov updated OVIRT-2792: --- Resolution: Duplicate Status: Done (was: To Do) This is a dublicate of docker

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #602 kubernetes-nmstate [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

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #153

See Changes: [Barak Korren] ost_build_resolver: Fix tests and small re-factor -- Started by timer Running as SYSTEM [EnvInject] - Loading

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5461 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5460 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5459 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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #700 vdsm [check-network]. 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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #700 vdsm [check-network]. 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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #700 vdsm [check-network]. 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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #700 vdsm [check-network]. 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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #601 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #601 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5458 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

[CQ]: 102680,17 (ovirt-engine) failed "ovirt-master" system tests

Change 102680,17 (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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #699 vdsm [check-network]. 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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #699 vdsm [check-network]. 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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #699 vdsm [check-network]. 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

[JENKINS] Failed to setup proejct standard-manual-runner

Failed to run project_setup.sh for: #699 vdsm [check-network]. 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

[JENKINS] Failed to setup proejct jenkins_gate

Failed to run project_setup.sh for: #93. 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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #600 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #600 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #599 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #599 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #598 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #598 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #597 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

Failed to run project_setup.sh for: #597 kubernetes-nmstate [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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5457 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5457 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5455 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5456 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5456 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5456 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

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

Failed to run project_setup.sh for: #5456 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

  1   2   >