- Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 824
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

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/824//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 47f3db5 (v2v-conversion-host) failed "ovirt-4.2" system tests
by oVirt Jenkins 13 May '19

13 May '19

Change 47f3db5 (v2v-conversion-host) 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 about the change see: https://github.com/oVirt/v2v-conversion-host/commit/47f3db53883f2133b5ba5e7… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4339/

1 0

[JIRA] (OVIRT-2727) Fwd: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer
by Greg Sheremeta (oVirt JIRA) 13 May '19

13 May '19

Greg Sheremeta created OVIRT-2727: ------------------------------------- Summary: Fwd: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer Key: OVIRT-2727 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2727 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Please grant Ales +2 access on ovirt-engine ---------- Forwarded message --------- From: Greg Sheremeta <gshereme(a)redhat.com> Date: Mon, May 13, 2019 at 2:52 PM Subject: Re: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer To: devel <devel(a)ovirt.org>, Ales Musil <amusil(a)redhat.com> Thanks everyone. Ales, congrats, and be careful :) On Mon, May 13, 2019 at 12:11 PM Tal Nisan <tnisan(a)redhat.com> wrote: > +1 > > On Thu, May 9, 2019 at 9:37 AM Tomas Jelinek <tjelinek(a)redhat.com> wrote: > >> >> >> On Sun, May 5, 2019 at 8:10 PM Daniel Erez <derez(a)redhat.com> wrote: >> >>> >>> >>> On Thu, May 2, 2019 at 9:42 PM Greg Sheremeta <gshereme(a)redhat.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> I'd like to propose Ales Musil as a frontend maintainer for network >>>> parts of the admin portal UI. Since joining the team 2 years ago, Ales has >>>> quickly become very knowledgeable about all of the GWT intricacies of the >>>> admin portal. I trust his expertise and judgment. >>>> >>> >> +1 fur sure! >> >> >>> >>> +1 >>> >>> >>>> >>>> Best wishes, >>>> Greg >>>> >>>> -- >>>> >>>> Greg Sheremeta >>>> >>>> Senior Software Engineer >>>> >>>> Red Hat <https://www.redhat.com/> >>>> <https://www.redhat.com/> >>>> _______________________________________________ >>>> Devel mailing list -- devel(a)ovirt.org >>>> To unsubscribe send an email to devel-leave(a)ovirt.org >>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ML5UVKYABG744… >>>> >>> _______________________________________________ >>> Devel mailing list -- devel(a)ovirt.org >>> To unsubscribe send an email to devel-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/N7WW4AWIZQII5… >>> >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QLLIXIVBQ2SKB… >> > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OWAOTCLUMK7LN… > -- Greg Sheremeta Senior Software Engineer, Service Delivery Red Hat <https://www.redhat.com/> <https://www.redhat.com/> -- Greg Sheremeta Senior Software Engineer, Service Delivery Red Hat <https://www.redhat.com/> <https://www.redhat.com/> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [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 lfedora1.lf-dev.marist.edu.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [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 lfedora1.lf-dev.marist.edu.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [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 lfedora1.lf-dev.marist.edu.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [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 vm0091.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [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 vm0089.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [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 vm0044.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [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 vm0038.workers-phx.ovirt.org.

1 0