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/707//artifact/exported-artifacts/upstream_report.html
Cheers,
Jenkins
Failed to run project_setup.sh for:
#3184 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 openshift-kubevirt-or
Failed to run project_setup.sh for:
#3182 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 openshift-kubevirt-or
Failed to run project_setup.sh for:
#3182 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 openshift-kubevirt-or
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38839#comment-38839
]
Laura Wright commented on OVIRT-2652:
-
Hi Roy,
I'm currently working on some redesign eff
Failed to run project_setup.sh for:
#1753 vdsm [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 vm0034.workers-phx.ovirt.
Failed to run project_setup.sh for:
#1737 vdsm [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 vm0040.workers-phx.ovirt.
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38836#comment-38836
]
Edward Haas commented on OVIRT-2651:
On Tue, Jan 15, 2019 at 9:01 PM Nir Soffer wrote:
>
On Tue, Jan 15, 2019 at 9:01 PM Nir Soffer wrote:
> See https://jenkins.ovirt.org/job/vdsm_standard-check-patch/
>
>
> https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_standard-check-patch/runs/1693/nodes/124/steps/376/log/?start=0
>
> https://jenkins.ovirt.org/blue/rest/o
On Tue, Jan 15, 2019 at 8:43 PM Nir Soffer wrote:
> On Tue, Jan 15, 2019 at 8:41 PM Nir Soffer wrote:
>
>>
>> On Tue, Jan 15, 2019 at 12:56 PM Nir Soffer wrote:
>>
>>> On Sun, Jan 13, 2019 at 10:34 AM Edward Haas wrote:
>>>
Thank you Nir.
I added an assert message to this last o
Hi all,
I've spent some time over the last two days going over all our slaves that
were offline and bringing them back online.
Some slaves were offline because of obvious technical issues (Usually
having to do with disk space), and I've fixed those issues as well as wrote
some patches to automati
11 matches
Mail list logo
