2:41 a.m.
Failed to run project_setup.sh for:
#5487 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-mq8df.
8:36 a.m.
Failed to run project_setup.sh for:
#5488 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-8nkz3.
8:37 a.m.
Failed to run project_setup.sh for:
#5488 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-4j9c0.
8:37 a.m.
Failed to run project_setup.sh for:
#5488 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-2g4w6.
8:37 a.m.
Failed to run project_setup.sh for:
#5488 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-9mz5b.
8:37 a.m.
Failed to run project_setup.sh for:
#5488 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-s3077.
8:37 a.m.
Failed to run project_setup.sh for:
#5488 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-t6gqj.
8:37 a.m.
Failed to run project_setup.sh for:
#5488 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-pvgfn.
8:37 a.m.
Failed to run project_setup.sh for:
#5488 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-2zshp.
8:37 a.m.
Failed to run project_setup.sh for:
#5488 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-qr47f.
8:38 a.m.
Failed to run project_setup.sh for:
#5488 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-8ph8j.
1897
days inactive
1897
days old
10 comments
1 participants
participants (1)
-
jenkins＠jenkins.phx.ovirt.org