March 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1288) Find out why Gerrit always fails re-basing when trying to submit more then 3 changes at once
by Barak Korren (oVirt JIRA) 30 Mar '17

30 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1288?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1288: -------------------------------- Summary: Find out why Gerrit always fails re-basing when trying to submit more then 3 changes at once (was: Find out why Gerti always failes rebasing when trying to submit more then 3 changes at once) > Find out why Gerrit always fails re-basing when trying to submit more then 3 changes at once > -------------------------------------------------------------------------------------------- > > Key: OVIRT-1288 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1288 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > > Gerrit has a feature where if you have multiple dependant patches, and they all have all the flags properly set, the submit button for changes with unmerged dependencies becomes 'Submit including parents' and lets you submit a whole set of changes at once. > I've found out that of you have more then 3 dependent changes in a chain, Gerrit will always fail submitting the 4th change and claim there is a rebase conflict, even when there is none. > This sounds like an artificial limitation, and we need to at least know where it comes from. And consider removing it. -- This message was sent by Atlassian JIRA (v1000.870.1#100039)

1 0

[JIRA] (OVIRT-1288) Find out why Gerti always failes rebasing when trying to submit more then 3 changes at once
by Barak Korren (oVirt JIRA) 30 Mar '17

30 Mar '17

Barak Korren created OVIRT-1288: ----------------------------------- Summary: Find out why Gerti always failes rebasing when trying to submit more then 3 changes at once Key: OVIRT-1288 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1288 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Gerrit/git Reporter: Barak Korren Assignee: infra Gerrit has a feature where if you have multiple dependant patches, and they all have all the flags properly set, the submit button for changes with unmerged dependencies becomes 'Submit including parents' and lets you submit a whole set of changes at once. I've found out that of you have more then 3 dependent changes in a chain, Gerrit will always fail submitting the 4th change and claim there is a rebase conflict, even when there is none. This sounds like an artificial limitation, and we need to at least know where it comes from. And consider removing it. -- This message was sent by Atlassian JIRA (v1000.870.1#100039)

1 0

[JIRA] (OVIRT-1288) Find out why Gerti always failes rebasing when trying to submit more then 3 changes at once
by Barak Korren (oVirt JIRA) 30 Mar '17

30 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1288?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1288: -------------------------------- Epic Link: OVIRT-403 > Find out why Gerti always failes rebasing when trying to submit more then 3 changes at once > ------------------------------------------------------------------------------------------- > > Key: OVIRT-1288 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1288 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > > Gerrit has a feature where if you have multiple dependant patches, and they all have all the flags properly set, the submit button for changes with unmerged dependencies becomes 'Submit including parents' and lets you submit a whole set of changes at once. > I've found out that of you have more then 3 dependent changes in a chain, Gerrit will always fail submitting the 4th change and claim there is a rebase conflict, even when there is none. > This sounds like an artificial limitation, and we need to at least know where it comes from. And consider removing it. -- This message was sent by Atlassian JIRA (v1000.870.1#100039)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #199
by jenkins＠jenkins.phx.ovirt.org 30 Mar '17

30 Mar '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/199/displa…> Changes: [Eyal Edri] removing jobs from master publisher - phase III [Daniel Belenky] jenkins: added a 'standard' support to export junit reports ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 74b0be04f3069503cfafc5b55a3d4d2b8c7ca0ce (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 74b0be04f3069503cfafc5b55a3d4d2b8c7ca0ce > git rev-list 7c3678caea37cd0d53a8cd5afbea3bcffa15a292 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson9181855977964224192.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 687, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 112, in retrieveAllMD repo._revertOldRepoXML() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1309, in _revertOldRepoXML os.rename(old_data['old_local'], old_data['local']) OSError: [Errno 2] No such file or directory Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 275
by jenkins＠jenkins.phx.ovirt.org 30 Mar '17

30 Mar '17

------=_Part_59_2016559958.1490828418213 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/275//artifact/exported-a… Cheers, Jenkins ------=_Part_59_2016559958.1490828418213 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 - 29/03/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_master-ansible-system-tests/">ovirt_master-ansible-system-tests</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/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</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/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</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-epel-el6-x86_64/">system-sync_mirrors-epel-el6-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_59_2016559958.1490828418213--

1 0

[ Announcment ] STD CI now supports custom junit reports
by Daniel Belenky 29 Mar '17

29 Mar '17

Hi all, The oVirt infra team is proud to announce that as from today the standard ci supports export of custom junit reports. *How to use?* Simply generate your junit .xml files, and follow the following naming: *<your_custom_name>.junit.xml. *Make sure you move them to exported-artifacts directory. That's all, the std ci will collect your .junit.xml files, and generate the junit report for you. Please feel free to contact the infra team on infra(a)ovirt.org for any more questions you have. Sincerely, -- *Daniel Belenky* *RHV DevOps* *Red Hat Israel*

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6084 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Mar '17

29 Mar '17

------=_Part_54_1881282753.1490797967310 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6084/, Build Number: 6084, Build Status: FAILURE ------=_Part_54_1881282753.1490797967310--

1 1

Change 34 [4] passed system tests
by oVirt Jenkins 29 Mar '17

29 Mar '17

Change 34 [4] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/34/ For test results of last test that included this change see: http://jenkins-staging.phx.ovirt.org/job/numbers_change-queue-tester/75/

1 0

Change 34 [4] queued for testing
by oVirt Jenkins 29 Mar '17

29 Mar '17

Change 34 [4] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/34/

1 0

Change 33 [7] failed system tests
by oVirt Jenkins 29 Mar '17

29 Mar '17

Change 33 [7] is probably the reason behind recent system test failures in the "numbers" 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: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/33/ For failed test results see: http://jenkins-staging.phx.ovirt.org/job/numbers_change-queue-tester/73/

1 0