Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/267/
Build Number: 267
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/267/
Build Number: 267
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
A system test invoked by the "ovirt-master" change queue including change
94087,7 (ovirt-imageio) failed. However, this change seems not to be the root
cause for this failure. Change 94243,5 (ovirt-imageio) that this change depends
on or is based on, was detected as the cause of the testing
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/267/
Build Number: 267
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/734/
Build Number: 734
Build Status: Still Failing
Triggered By: Started by timer
-
Change 1e8001a (ovirt-ansible-v2v-conversion-host) 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
A system test invoked by the "ovirt-master" change queue including change
94237,7 (ovirt-imageio) failed. However, this change seems not to be the root
cause for this failure. Change 94243,5 (ovirt-imageio) that this change depends
on or is based on, was detected as the cause of the testing
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/798/
Build Number: 798
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/780/
Build Number: 780
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
Project:
http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7-x86_64/
Build:
http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7-x86_64/88/
Build Number: 88
Build Status: Still Failing
Triggered By: Started by timer
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/680/
Build Number: 680
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since Last
Failed to run project_setup.sh for:
#2298 kubevirt [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
Failed to run project_setup.sh for:
#2300 kubevirt [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
Failed to run project_setup.sh for:
#2300 kubevirt [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
Failed to run project_setup.sh for:
#2301 kubevirt [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
Failed to run project_setup.sh for:
#2301 kubevirt [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
Failed to run project_setup.sh for:
#2302 kubevirt [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
Failed to run project_setup.sh for:
#2303 kubevirt [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
Failed to run project_setup.sh for:
#2304 kubevirt [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
Failed to run project_setup.sh for:
#2305 kubevirt [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
Failed to run project_setup.sh for:
#2297 kubevirt [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
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38251#comment-38251
]
Dafna Ron commented on OVIRT-2542:
--
https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3378/
>
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/799/
Build Number: 799
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dafna Ron updated OVIRT-2542:
-
Labels: ost_failures (was: ost_failures ost_race)
> several failures failures on host not being
Failed to run project_setup.sh for:
#2301 kubevirt [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
Failed to run project_setup.sh for:
#2302 kubevirt [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
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/781/
Build Number: 781
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
Failed to run project_setup.sh for:
#2303 kubevirt [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
Failed to run project_setup.sh for:
#2304 kubevirt [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
Failed to run project_setup.sh for:
#2305 kubevirt [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
Failed to run project_setup.sh for:
#2297 kubevirt [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
Failed to run project_setup.sh for:
#2298 kubevirt [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
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/681/
Build Number: 681
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since Last
Failed to run project_setup.sh for:
#2301 kubevirt [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
Failed to run project_setup.sh for:
#2304 kubevirt [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
Failed to run project_setup.sh for:
#2298 kubevirt [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
Change 95000,2 (ovirt-provider-ovn) 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
A system test invoked by the "ovirt-master" change queue including change
94026,8 (ovirt-imageio) failed. However, this change seems not to be the root
cause for this failure. Change 94243,5 (ovirt-imageio) that this change depends
on or is based on, was detected as the cause of the testing
Failed to run project_setup.sh for:
#2302 kubevirt [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
Failed to run project_setup.sh for:
#2302 kubevirt [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
Failed to run project_setup.sh for:
#2303 kubevirt [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
Failed to run project_setup.sh for:
#2303 kubevirt [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
Failed to run project_setup.sh for:
#2305 kubevirt [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
Failed to run project_setup.sh for:
#2305 kubevirt [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
Failed to run project_setup.sh for:
#2298 kubevirt [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
Failed to run project_setup.sh for:
#2300 kubevirt [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
Failed to run project_setup.sh for:
#2301 kubevirt [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
Failed to run project_setup.sh for:
#2304 kubevirt [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
Failed to run project_setup.sh for:
#2305 kubevirt [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
Failed to run project_setup.sh for:
#2297 kubevirt [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
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/898/
Build Number: 898
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/267/
Build Number: 267
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
Failed to run project_setup.sh for:
#2298 kubevirt [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
Failed to run project_setup.sh for:
#2303 kubevirt [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
Failed to run project_setup.sh for:
#2303 kubevirt [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
Failed to run project_setup.sh for:
#2304 kubevirt [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
Failed to run project_setup.sh for:
#2304 kubevirt [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
Failed to run project_setup.sh for:
#2305 kubevirt [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
A system test invoked by the "ovirt-master" change queue including change
94086,7 (ovirt-imageio) failed. However, this change seems not to be the root
cause for this failure. Change 94243,5 (ovirt-imageio) that this change depends
on or is based on, was detected as the cause of the testing
Failed to run project_setup.sh for:
#2298 kubevirt [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
Failed to run project_setup.sh for:
#2302 kubevirt [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
Failed to run project_setup.sh for:
#2302 kubevirt [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
Failed to run project_setup.sh for:
#2303 kubevirt [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
Failed to run project_setup.sh for:
#2297 kubevirt [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
Failed to run project_setup.sh for:
#2297 kubevirt [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
Failed to run project_setup.sh for:
#2299 kubevirt [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
Failed to run project_setup.sh for:
#2301 kubevirt [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
Failed to run project_setup.sh for:
#2304 kubevirt [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
Failed to run project_setup.sh for:
#2304 kubevirt [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
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/268/
Build Number: 268
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.0-suite-master/268/
Build Number: 268
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
Failed to run project_setup.sh for:
#2305 kubevirt [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
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/416/
Build Number: 416
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since Last
A system test invoked by the "ovirt-master" change queue including change
94057,8 (ovirt-imageio) failed. However, this change seems not to be the root
cause for this failure. Change 94243,5 (ovirt-imageio) that this change depends
on or is based on, was detected as the cause of the testing
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/624/
Build Number: 624
Build Status: Still Failing
Triggered By: Started by timer
-
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/673/
Build Number: 673
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since Last
A system test invoked by the "ovirt-master" change queue including change
94056,10 (ovirt-imageio) failed. However, this change seems not to be the root
cause for this failure. Change 94243,5 (ovirt-imageio) that this change depends
on or is based on, was detected as the cause of the testing
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/268/
Build Number: 268
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/579/
Build Number: 579
Build Status: Fixed
Triggered By: Started by timer
-
Changes Since Last Success:
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/415/
Build Number: 415
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
Failed to run project_setup.sh for:
#2308 kubevirt [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
Failed to run project_setup.sh for:
#2308 kubevirt [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
A system test invoked by the "ovirt-master" change queue including change
94085,7 (ovirt-imageio) failed. However, this change seems not to be the root
cause for this failure. Change 94243,5 (ovirt-imageio) that this change depends
on or is based on, was detected as the cause of the testing
A system test invoked by the "ovirt-master" change queue including change
74b0e9e (ovirt-ansible-v2v-conversion-host) failed. However, this change seems
not to be the root cause for this failure. Change 1e8001a (ovirt-ansible-v2v-
conversion-host) that this change depends on or is based on, was
Failed to run project_setup.sh for:
#2306 kubevirt [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
Failed to run project_setup.sh for:
#2308 kubevirt [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
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/899/
Build Number: 899
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since
A system test invoked by the "ovirt-master" change queue including change
94137,6 (ovirt-imageio) failed. However, this change seems not to be the root
cause for this failure. Change 94243,5 (ovirt-imageio) that this change depends
on or is based on, was detected as the cause of the testing
Failed to run project_setup.sh for:
#2308 kubevirt [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
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/268/
Build Number: 268
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/736/
Build Number: 736
Build Status: Still Failing
Triggered By: Started by timer
-
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/618//artifact/exported-artifacts/upstream_report.html
Cheers,
Jenkins
Change 94935,3 (ovirt-provider-ovn) 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
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/482/
Build Number: 482
Build Status: Still Failing
Triggered By: Started by timer
-
Changes
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/800/
Build Number: 800
Build Status: Fixed
Triggered By: Started by timer
-
Changes Since Last
Failed to run project_setup.sh for:
#2307 kubevirt [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
Failed to run project_setup.sh for:
#491 containerized-data-importer [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
Failed to run project_setup.sh for:
#2309 kubevirt [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
Failed to run project_setup.sh for:
#492 containerized-data-importer [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
Change 94935,3 (ovirt-provider-ovn) 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
1 - 100 of 139 matches
Mail list logo
