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/736//artifact/exported-artifacts/upstream_report.html
Cheers,
Jenkins
Failed to run project_setup.sh for:
#3593 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:
#3593 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:
#3593 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:
#3593 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:
#3591 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
97767,1 (ovirt-vmconsole) failed. However, this change seems not to be the root
cause for this failure. Change 97704,6 (ovirt-vmconsole) that this change
depends on or is based on, was detected as the cause of the testing
Failed to run project_setup.sh for:
#3587 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 97704,6 (ovirt-vmconsole) 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
Failed to run project_setup.sh for:
#239 ovirt-provider-ovn [check-merged].
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:
#239 ovirt-provider-ovn [check-merged].
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
YumBaseError: [u'ovirt-vmconsole-1.0.6-3.el7.noarch requires
selinux-policy >= 3.13.1-229.el7_6.9',
u'ovirt-vmconsole-1.0.6-3.el7.noarch requires selinux-policy-base >=
3.13.1-229.el7_6.9']
checking issue
On Thu, Feb 14, 2019 at 1:33 PM oVirt Jenkins wrote:
> Change 97704,6 (ovirt-vmconsole)
Failed to run project_setup.sh for:
#3581 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:
#3581 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 97704,6 (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
a new version of dpdk was causing issues.
Sandro tagged the new version and should be landing in centos soon
On Thu, Feb 14, 2019 at 11:54 AM oVirt Jenkins wrote:
> Change 97721,2 (vdsm) is probably the reason behind recent system test
> failures
> in the "ovirt-master" change queue and needs
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38998#comment-38998
]
Roman Mohr commented on OVIRT-2617:
---
So think about sprint ends. Many people have PRs, they produce load.
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38997#comment-38997
]
Roman Mohr commented on OVIRT-2617:
---
Well if one suspicious lane fails, we write "retest this please". This
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38996#comment-38996
]
Roman Mohr commented on OVIRT-2590:
---
Thinking about our CI images it can avoid peaks on the network
We are failing upgrade suite on host deploy due to missing dpdk package.
I added a patch to fix it: https://gerrit.ovirt.org/97762
On Thu, Feb 14, 2019 at 8:21 AM oVirt Jenkins wrote:
> A system test invoked by the "ovirt-master" change queue including change
> 97733,2 (ovirt-engine) failed.
On Thu, Feb 14, 2019 at 9:56 AM oVirt Jenkins wrote:
>
> A system test invoked by the "ovirt-master" change queue including change
> 97694,4 (ovirt-engine) failed. However, this change seems not to be the root
> cause for this failure. Change 97726,5 (ovirt-engine) that this change depends
> on
A system test invoked by the "ovirt-master" change queue including change
97733,2 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 97726,5 (ovirt-engine) that this change depends
on or is based on, was detected as the cause of the testing
22 matches
Mail list logo
