- Infra - oVirt List Archives

[JIRA] (OVIRT-1739) Unified code owners mechanism between Gerrit and GitHub
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1739?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1739: -------------------------------- Labels: gerrit github reviewers standard-ci (was: ) > Unified code owners mechanism between Gerrit and GitHub > ------------------------------------------------------- > > Key: OVIRT-1739 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git, GitHub, oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: gerrit, github, reviewers, standard-ci > > "Code owners" is the mechanism that automatically assigns reviewers to new code patches. > In Gerrit we use the "reviewers" plugin to automatically set reviewers (See OVIRT-1165). > GitHub has its own mechanism: https://github.com/blog/2392-introducing-code-owners > We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[CQ]: 83612,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 06 Nov '17

06 Nov '17

Change 83612,2 (ovirt-engine) 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 about the change see: https://gerrit.ovirt.org/#/c/83612/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3626/

1 0

[JIRA] (OVIRT-1739) Unified code owners mechanism between Gerrit and GitHub
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1739?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1739: ------------------------------------- Current direction is to add support for this in the '{{automation.yaml}}' format so that the default behaviour would be to support the GitHub format. Adding OVIRT-1629 as a blocker to this ticket. > Unified code owners mechanism between Gerrit and GitHub > ------------------------------------------------------- > > Key: OVIRT-1739 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git, GitHub, oVirt CI > Reporter: Barak Korren > Assignee: infra > > "Code owners" is the mechanism that automatically assigns reviewers to new code patches. > In Gerrit we use the "reviewers" plugin to automatically set reviewers (See OVIRT-1165). > GitHub has its own mechanism: https://github.com/blog/2392-introducing-code-owners > We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1739) Unified code owners mechanism between Gerrit and GitHub
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1739?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1739: -------------------------------- Epic Link: OVIRT-400 > Unified code owners mechanism between Gerrit and GitHub > ------------------------------------------------------- > > Key: OVIRT-1739 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git, GitHub, oVirt CI > Reporter: Barak Korren > Assignee: infra > > "Code owners" is the mechanism that automatically assigns reviewers to new code patches. > In Gerrit we use the "reviewers" plugin to automatically set reviewers (See OVIRT-1165). > GitHub has its own mechanism: https://github.com/blog/2392-introducing-code-owners > We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1739) Unified code owners mechanism between Gerrit and GitHub
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

This is a multi-part message in MIME format... ------------=_1509956867-24534-179 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1739: ----------------------------------- Summary: Unified code owners mechanism between Gerrit and GitHub Key: OVIRT-1739 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git, GitHub, oVirt CI Reporter: Barak Korren Assignee: infra "Code owners" is the mechanism that automatically assigns reviewers to new code patches. In Gerrit we use the "reviewers" plugin to automatically set reviewers (See OVIRT-1165). GitHub has its own mechanism: https://github.com/blog/2392-introducing-code-owners We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1509956867-24534-179 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1739:</h3> <pre> Summary: Unified code owners mechanism between Gerrit and GitHub Key: OVIRT-1739 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git, GitHub, oVirt CI Reporter: Barak Korren Assignee: infra</pre> <p>“Code owners” is the mechanism that automatically assigns reviewers to new code patches.</p> <p>In Gerrit we use the “reviewers” plugin to automatically set reviewers (See OVIRT-1165).</p> <p>GitHub has its own mechanism: <a href="https://github.com/blog/2392-introducing-code-owners">https://github.com/blog/2392-introducing-code-owners</a></p> <p>We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1509956867-24534-179--

1 0

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1732: -------------------------------- Priority: High (was: Medium) > Make 'poll-upstream-chages' job abandon old changes it made > ----------------------------------------------------------- > > Key: OVIRT-1732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: poll-upstream-sources, standard-ci > > The poll-upstream-changes job creates patches when it runs. Not all these patches need or should be merged. When maintainers get around to looking at them, they typically can just merge the latest patch and throw away the rest. > The issue is that over time, the patches created by the job can accumulate, and it can be cumbersome for maintainers to remove un-needed ones manually. > We should make the poll job remove un-needed patches it made. It needs to look at the last SHA in the upstream-sources.yaml file, and remove all that patches that include an older SHA automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

oVirt infra daily report - unstable production jobs - 496
by jenkins＠jenkins.phx.ovirt.org 05 Nov '17

05 Nov '17

------=_Part_54_544170131.1509922802665 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/496//artifact/exported-a… Cheers, Jenkins ------=_Part_54_544170131.1509922802665 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 - 05/11/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/ovirt-system-tests_ansible-suite-master/">ovirt-system-tests_ansible-suite-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> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-centos-extras-el7-x86_64/">system-sync_mirrors-centos-extras-el7-x86_64</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_54_544170131.1509922802665--

1 0

[CQ]: 83344, 2 (ovirt-engine) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Nov '17

05 Nov '17

A system test invoked by the "ovirt-4.1" change queue including change 83344,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 82995,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 82995,4 (ovirt-engine) 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/83344/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/82995/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1273/

1 0

[CQ]: 82843, 7 (ovirt-engine) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Nov '17

05 Nov '17

A system test invoked by the "ovirt-4.1" change queue including change 82843,7 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 82995,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 82995,4 (ovirt-engine) 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/82843/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/82995/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1272/

1 0

[JIRA] (OVIRT-1702) Jenkins STD-CI are running in dirty mock chroots
by Barak Korren (oVirt JIRA) 05 Nov '17

05 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1702?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1702: ------------------------------------- {quote} I'm pretty sure in the past it was completely removed from the slave. {quote} I'm pretty sure it was not, since code handling this has not been significantly changed since David first wrote it. The workspace including the source checkout does get completely remove when a *different job* starts running on the node. But as long as its the same job, the workspace stays as-is. {quote} Is there any good reason for not cleaning the slave after job completion? {quote} Yes. Re-cloning the whole git repo every time we run something will significantly slow things down. Also we do not clean the slave up *after* the execution, we clean it *before the next one*. This has the benefit of allowing us to debug failed runs and also prevent the next run from failing if the post-run code was not reached for some reason. But a side-affect of this is that the more cleanup steps we have the longer the latency our users experience between submitting patchs and having their check-patch code run, so we try to keep it to a minimum. > Jenkins STD-CI are running in dirty mock chroots > ------------------------------------------------ > > Key: OVIRT-1702 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1702 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Example: > http://jenkins.ovirt.org/job/ovirt-wgt_master_check-patch-fc26-x86_64/11/co… > *09:44:06* + ./automation/build-artifacts.sh*09:44:06* + [[ -d > exported-artifacts ]]*09:44:06* + mkdir -p > exported-artifacts*09:44:06* + [[ -d tmp.repos/SOURCES ]]*09:44:06* + > mkdir -p tmp.repos/SOURCES*09:44:06* + git clone > git://anongit.freedesktop.org/spice/spice-nsis*09:44:06* fatal: > destination path 'spice-nsis' already exists and is not an empty > directory. > jobs should run in clean chroots. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > <http://www.teraplan.it/redhat-osd-2017/> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0