Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #448
by jenkins@jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/448/disp...>
------------------------------------------
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/changes/13/75913/5:patch --prune
> git rev-parse origin/patch^{commit} # timeout=10
> git rev-parse patch^{commit} # timeout=10
Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch)
> git config core.sparsecheckout # timeout=10
> git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f
> git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10
[system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson979789285606340572.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
if self._latestRepoXML(local):
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML
repomd = self.metalink_data.repomd
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 916, in <lambda>
metalink_data = property(fget=lambda self: self._getMetalink(),
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 904, in _getMetalink
shutil.move(result, self.metalink_filename)
File "/usr/lib64/python2.7/shutil.py", line 301, in move
copy2(src, real_dst)
File "/usr/lib64/python2.7/shutil.py", line 130, in copy2
copyfile(src, dst)
File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile
with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-base-fc25/metalink.xml.tmp'
Build step 'Execute shell' marked build as failure
7 years, 5 months
oVirt infra daily report - unstable production jobs - 357
by jenkins@jenkins.phx.ovirt.org
------=_Part_546_331205793.1497826801683
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/357//artifact/exported...
Cheers,
Jenkins
------=_Part_546_331205793.1497826801683
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 - 18/06/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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
------=_Part_546_331205793.1497826801683--
7 years, 5 months
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1448:
-------------------------------------
Created [a patch|https://gerrit.ovirt.org/78277] to fix a code issue that would have prevented us from properly implementing dependencies for merged Gerrit changes.
> Enable devs to specifiy patch dependencies for OST
> --------------------------------------------------
>
> Key: OVIRT-1448
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
> Labels: change-queue
>
> We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency.
> What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged.
> The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test.
> The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies.
> We would probably want to adopt OpenStack's convention here.
--
This message was sent by Atlassian JIRA
(v1000.1068.0#100050)
7 years, 5 months
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1448:
-------------------------------------
Here are some docs about how this is done in OpenStack:
https://docs.openstack.org/infra/manual/developers.html#cross-repository-...
The basic Idea is that developers add a '{{Depends-On:}}' header to the commit message follows by a 40-char Gerrit change ID.
One implication of this is that the same change ID can point to multiple changes (same change in different branches), so we will need to query Gerrit and find all actual changes with that ID.
> Enable devs to specifiy patch dependencies for OST
> --------------------------------------------------
>
> Key: OVIRT-1448
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
> Labels: change-queue
>
> We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency.
> What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged.
> The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test.
> The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies.
> We would probably want to adopt OpenStack's convention here.
--
This message was sent by Atlassian JIRA
(v1000.1068.0#100050)
7 years, 5 months