Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1196
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1196/dis...>
------------------------------------------
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 633e9a8b0cddbe18f68cd295f21a60e6675558be (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 633e9a8b0cddbe18f68cd295f21a60e6675558be
Commit message: "ovirt-host: drop s390x fcraw jobs"
> git rev-list 633e9a8b0cddbe18f68cd295f21a60e6675558be # timeout=10
[system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins5013792939690223846.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 681, in doRepoSetup
return self._getRepos(thisrepo, True)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, 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 88, in retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML
local = self.cachedir + '/repomd.xml'
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda>
cachedir = property(lambda self: self._dirGetAttr('cachedir'))
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr
self.dirSetup()
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup
self._dirSetupMkdir_p(dir)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p
raise Errors.RepoError, msg
yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7'
Build step 'Execute shell' marked build as failure
6 years, 10 months
[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1518592373-16157-109
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1895:
--------------------------------
Resolution: Duplicate
Status: Done (was: To Do)
> CI votes not forwarded on commit message change
> -----------------------------------------------
>
> Key: OVIRT-1895
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Gerrit/git
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> Hi all,
> If a change goes through this flow:
> 1. Push an update N
> 2. CI triggers check-patch for N
> 3. Push another update N+1 that changes only commit message
> 4. CI marks +1 N
> Then we have logic to not trigger CI for N+1 (with the assumption that
> a change to commit message should not affect the result), but also do
> not mark +1 N+1, leaving the patch unmarked.
> We should either forward the +1, when giving it, to all consecutive
> future patchsets that only changed the commit message, or give up on
> the optimization and always trigger CI.
> As an example, see:
> https://gerrit.ovirt.org/87515
> Best regards,
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100079)
------------=_1518592373-16157-109
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jir... ]</pre>
<h3>Barak Korren updated OVIRT-1895:</h3>
<pre>Resolution: Duplicate
Status: Done (was: To Do)</pre>
<blockquote><h3>CI votes not forwarded on commit message change</h3>
<pre> Key: OVIRT-1895
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: Gerrit/git
Reporter: Yedidyah Bar David
Assignee: infra</pre>
<p>Hi all, If a change goes through this flow:</p>
<ol><li><p>Push an update N</p></li>
<li><p>CI triggers check-patch for N</p></li>
<li><p>Push another update N+1 that changes only commit message</p></li>
<li><p>CI marks +1 N</p></li></ol>
<p>Then we have logic to not trigger CI for N+1 (with the assumption that a change to commit message should not affect the result), but also do not mark +1 N+1, leaving the patch unmarked. We should either forward the +1, when giving it, to all consecutive future patchsets that only changed the commit message, or give up on the optimization and always trigger CI. As an example, see: <a href="https://gerrit.ovirt.org/87515">https://gerrit.ovirt.org/87515</a> Best regards, — Didi</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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>
------------=_1518592373-16157-109--
6 years, 10 months
[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1518592365-27516-116
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1895:
--------------------------------
Component/s: Gerrit/git
Epic Link: OVIRT-400
Issue Type: Bug (was: By-EMAIL)
> CI votes not forwarded on commit message change
> -----------------------------------------------
>
> Key: OVIRT-1895
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Gerrit/git
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> Hi all,
> If a change goes through this flow:
> 1. Push an update N
> 2. CI triggers check-patch for N
> 3. Push another update N+1 that changes only commit message
> 4. CI marks +1 N
> Then we have logic to not trigger CI for N+1 (with the assumption that
> a change to commit message should not affect the result), but also do
> not mark +1 N+1, leaving the patch unmarked.
> We should either forward the +1, when giving it, to all consecutive
> future patchsets that only changed the commit message, or give up on
> the optimization and always trigger CI.
> As an example, see:
> https://gerrit.ovirt.org/87515
> Best regards,
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100079)
------------=_1518592365-27516-116
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jir... ]</pre>
<h3>Barak Korren updated OVIRT-1895:</h3>
<pre>Component/s: Gerrit/git
Epic Link: OVIRT-400
Issue Type: Bug (was: By-EMAIL)</pre>
<blockquote><h3>CI votes not forwarded on commit message change</h3>
<pre> Key: OVIRT-1895
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: Gerrit/git
Reporter: Yedidyah Bar David
Assignee: infra</pre>
<p>Hi all, If a change goes through this flow:</p>
<ol><li><p>Push an update N</p></li>
<li><p>CI triggers check-patch for N</p></li>
<li><p>Push another update N+1 that changes only commit message</p></li>
<li><p>CI marks +1 N</p></li></ol>
<p>Then we have logic to not trigger CI for N+1 (with the assumption that a change to commit message should not affect the result), but also do not mark +1 N+1, leaving the patch unmarked. We should either forward the +1, when giving it, to all consecutive future patchsets that only changed the commit message, or give up on the optimization and always trigger CI. As an example, see: <a href="https://gerrit.ovirt.org/87515">https://gerrit.ovirt.org/87515</a> Best regards, — Didi</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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>
------------=_1518592365-27516-116--
6 years, 10 months
[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1895:
--------------------------------
Epic Link: OVIRT-400
> CI votes not forwarded on commit message change
> -----------------------------------------------
>
> Key: OVIRT-1895
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Components: Gerrit/git
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> Hi all,
> If a change goes through this flow:
> 1. Push an update N
> 2. CI triggers check-patch for N
> 3. Push another update N+1 that changes only commit message
> 4. CI marks +1 N
> Then we have logic to not trigger CI for N+1 (with the assumption that
> a change to commit message should not affect the result), but also do
> not mark +1 N+1, leaving the patch unmarked.
> We should either forward the +1, when giving it, to all consecutive
> future patchsets that only changed the commit message, or give up on
> the optimization and always trigger CI.
> As an example, see:
> https://gerrit.ovirt.org/87515
> Best regards,
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100079)
6 years, 10 months
[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1895:
-------------------------------------
[~didi(a)redhat.com] this had been reported many times in the past including by you in OVIRT-1627.
See OVIRT-1639 for a tracker for solving this.
Closing this ticket as a duplicate
> CI votes not forwarded on commit message change
> -----------------------------------------------
>
> Key: OVIRT-1895
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> Hi all,
> If a change goes through this flow:
> 1. Push an update N
> 2. CI triggers check-patch for N
> 3. Push another update N+1 that changes only commit message
> 4. CI marks +1 N
> Then we have logic to not trigger CI for N+1 (with the assumption that
> a change to commit message should not affect the result), but also do
> not mark +1 N+1, leaving the patch unmarked.
> We should either forward the +1, when giving it, to all consecutive
> future patchsets that only changed the commit message, or give up on
> the optimization and always trigger CI.
> As an example, see:
> https://gerrit.ovirt.org/87515
> Best regards,
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100079)
6 years, 10 months
