- Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 372
by jenkins＠jenkins.phx.ovirt.org 03 Jul '17

03 Jul '17

------=_Part_161_1745765684.1499122801872 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/372//artifact/exported-a… Cheers, Jenkins ------=_Part_161_1745765684.1499122801872 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 03/07/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_161_1745765684.1499122801872--

1 0

[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure
by ngoldin＠redhat.com (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-713?page=com.atlassian.jira.p… ] ngoldin(a)redhat.com commented on OVIRT-713: ------------------------------------------ I didn't see any failures with this at least in the past 2 months. We added some fixes to reposync flow, but that was a while ago. > Clean reposync directory after n times of sync failure > ------------------------------------------------------ > > Key: OVIRT-713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: infra > > Sometimes reposync fail to sync rpms that already been synced. > To resolve this issue, lago removes those rpms, and runs reposync again. > This resolution doesn't always work, and then we need to clean all the rpms that were synced. > We want lago to clear the cached rpms after n times of sync failure, and then try to sync again. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

Change 78631,13 (vdsm) failed system tests
by oVirt Jenkins 03 Jul '17

03 Jul '17

A system test invoked by the "ovirt-master" change queue including change 78631,13 (vdsm) failed. However, this change seems not to be to root cause for failure. Change 78630,13 (vdsm) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78630,13 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/78631/13 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78630/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1049/

1 0

Change 78837,4 (vdsm) failed system tests
by oVirt Jenkins 03 Jul '17

03 Jul '17

A system test invoked by the "ovirt-master" change queue including change 78837,4 (vdsm) failed. However, this change seems not to be to root cause for failure. Change 78630,13 (vdsm) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78630,13 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/78837/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78630/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1047/

1 0

Change 78890,3 (vdsm) failed system tests
by oVirt Jenkins 03 Jul '17

03 Jul '17

A system test invoked by the "ovirt-master" change queue including change 78890,3 (vdsm) failed. However, this change seems not to be to root cause for failure. Change 78630,13 (vdsm) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78630,13 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/78890/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78630/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1039/

1 0

[JIRA] (OVIRT-1434) Re: Every user can abandon patches that are not his
by Shlomo Ben David (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1434?page=com.atlassian.jira.… ] Shlomo Ben David updated OVIRT-1434: ------------------------------------ Resolution: Fixed Status: Done (was: To Do) > Re: Every user can abandon patches that are not his > --------------------------------------------------- > > Key: OVIRT-1434 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1434 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: Shlomo Ben David > > Adding infra support to open a ticket. > On Wed, Jun 7, 2017 at 3:11 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Hi, > > I've discovered that every user can abandon patches even if they are not > > his, here's an example of Shani abandoning my patch which shouldn't be > > allowed: > > > > https://gerrit.ovirt.org/#/c/77919/ > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal edri > ASSOCIATE MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1434) Re: Every user can abandon patches that are not his
by Shlomo Ben David (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1434?page=com.atlassian.jira.… ] Shlomo Ben David commented on OVIRT-1434: ----------------------------------------- yes, with this patch: https://gerrit.ovirt.org/#/c/77941/ > Re: Every user can abandon patches that are not his > --------------------------------------------------- > > Key: OVIRT-1434 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1434 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: Shlomo Ben David > > Adding infra support to open a ticket. > On Wed, Jun 7, 2017 at 3:11 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Hi, > > I've discovered that every user can abandon patches even if they are not > > his, here's an example of Shani abandoning my patch which shouldn't be > > allowed: > > > > https://gerrit.ovirt.org/#/c/77919/ > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal edri > ASSOCIATE MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #1800 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 03 Jul '17

03 Jul '17

------=_Part_145_102059630.1499098923494 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1800/, Build Number: 1800, Build Status: FAILURE ------=_Part_145_102059630.1499098923494--

1 1

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1252: ------------------------------------- [~eedri] yes. for when using build-artifats as a yum repo with the latestStableBuild link. > post-merge build-artifacts jobs can run out of order > ---------------------------------------------------- > > Key: OVIRT-1252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. > The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. > To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1162) Make sure cron failure email from resources.ovirt.org reach the infra list
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1162?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1162: ------------------------------------- [~eedri] actually I made the nightly publisher jobs check if cron ran and fail (with unstable) otherwise when I made it sync from tested. So this is probably not highly needed any more. > Make sure cron failure email from resources.ovirt.org reach the infra list > -------------------------------------------------------------------------- > > Key: OVIRT-1162 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1162 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > > There are quite a few things that run there with cron and we need to know when they fail. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0