2:29 a.m.
Failed to run project_setup.sh for:
#5467 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-0wxjs.
4:12 a.m.
Failed to run project_setup.sh for:
#5468 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-d920m.
4:12 a.m.
Failed to run project_setup.sh for:
#5468 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-3mjvv.
4:13 a.m.
Failed to run project_setup.sh for:
#5468 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-m4hn4.
4:13 a.m.
Failed to run project_setup.sh for:
#5468 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-lz475.
4:13 a.m.
Failed to run project_setup.sh for:
#5468 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-cr2kl.
4:13 a.m.
Failed to run project_setup.sh for:
#5468 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-g4w3v.
4:13 a.m.
Failed to run project_setup.sh for:
#5468 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-tbmck.
4:13 a.m.
Failed to run project_setup.sh for:
#5468 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-g6v7m.
4:13 a.m.
Failed to run project_setup.sh for:
#5468 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-gzh18.
4:14 a.m.
Failed to run project_setup.sh for:
#5468 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-gfk66.
1691
days inactive
1691
days old
10 comments
1 participants
participants (1)
-
jenkins＠jenkins.phx.ovirt.org