[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:
#357 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-2pgbl.
5 years, 2 months
[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:
#357 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-4dr73.
5 years, 2 months
[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:
#357 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-bpc7z.
5 years, 2 months
[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:
#357 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-418qh.
5 years, 2 months
[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:
#357 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-90db6.
5 years, 2 months
[oVirt] [CQ weekly status] [13-09-2019]
by Dusan Fodor
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.3*: GREEN (#3)
No failure this week.
*CQ-Master:* RED (#1)
Last failure was on 12-09 was for ovirt-engine on adding storage domain.
The issue is under investigation under thread "random failures for
add_master_storage_domain".
Current running jobs for 4.3 [1] and master [2] can be found here:
[1] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt
-4.3_change-queue-tester/
[2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt
-master_change-queue-tester/
Have a nice week!
Dusan
-------------------------------------------------------------------------------------------------------------------
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)
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt
.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt
.org/message/YCNCKRK3G4EJXA3OCYAUS4VMKRDA67F4/
5 years, 2 months
[JENKINS] Failed to setup proejct
vdsm_master_standard-poll-upstream-sources
by jenkins@jenkins.phx.ovirt.org
Failed to run project_setup.sh for:
#8 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 openshift-integ-tests-container-tzw0w.
5 years, 2 months
[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:
#356 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-t90bg.
5 years, 2 months
[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:
#356 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-38lr4.
5 years, 2 months