oVirt infra daily report - unstable production jobs - 223
by jenkins@jenkins.phx.ovirt.org
------=_Part_88_331661398.1486422007045
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/223//artifact/exported...
Cheers,
Jenkins
------=_Part_88_331661398.1486422007045
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 - 06/02/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-live_master_experimental_create-iso-el...">ovirt-live_master_experimental_create-iso-el7-x86_64</a>
</td><td>
<h3>This job generates a nightly iso of ovirt-live using experimental repos</h3>
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_buil...">ovirt-node-ng_ovirt-master-experimental_build-artifacts-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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x...">ovirt-system-tests_master_check-patch-fc24-x86_64_archived_for_deletion</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>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/">ovirt_4.0_he-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>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.1_system-tests_pre/">ovirt_4.1_system-tests_pre</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>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</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>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</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>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</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_88_331661398.1486422007045--
7 years, 9 months
[JIRA] (OVIRT-1110) rpms served from new jenkins repos sometimes timeout with "xyz bytes remaining to read"
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1110?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1110:
-------------------------------------
I wonder, are we seeing a race condition where the other package is built at the same time?
It also may be our squid proxy acting up, but you don't really need to use it because jenkins and the node running the job are in the same datacenter.
Does this happen frequently enough that we can reliably test a work around?
The following should disable proxy usage from inside mock:
{code}
sed -i -re 's/^(proxy *= *).*$/\1_none_/' /etc/yum/yum.conf
http_proxy=''
{code}
If this works we will probably need to make mock_runner do this automatically for all repos local to PHX.
> rpms served from new jenkins repos sometimes timeout with "xyz bytes remaining to read"
> ---------------------------------------------------------------------------------------
>
> Key: OVIRT-1110
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1110
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Greg Sheremeta
> Assignee: infra
>
> I'm running mock_runner locally.
> ../jenkins/mock_configs/mock_runner.sh --mock-confs-dir
> ../jenkins/mock_configs el7:epel-7-x86_64 --patch-only
> I've seen this error about 5 times when using the new jenkins-based mini
> repos:
> <snip>
> Total download size: 162 M
> Installed size: 515 M
> http://jenkins.ovirt.org/job/ovirt-engine-nodejs_master_build-artifacts-e...:
> [Errno 14] curl#18 - "transfer closed with 2444831 bytes remaining to read"
> Trying other mirror.
> When I try once more, I always get this error:
> Installed size: 515 M
> No Presto metadata available for ovirt-engine-nodejs_master
> http://jenkins.ovirt.org/job/ovirt-engine-nodejs_master_build-artifacts-e...:
> [Errno -1] Package does not match intended download. Suggestion: run yum
> --enablerepo=ovirt-engine-nodejs_master clean metadata and try again
> Trying other mirror.
> And the final third time works.
> Any ideas?
> --
> Greg Sheremeta, MBA
> Red Hat, Inc.
> Sr. Software Engineer
> gshereme(a)redhat.com
--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
7 years, 9 months
planned mailman restart
by Evgheni Dereveanchin
Hi everyone,
In a couple of minutes I will reboot the server
hosting all of our mailing lists (including this one)
to install software updates. It should come up quickly,
but if you have any problems sending to oVirt lists
please try again after a few minutes.
I will announce you as soon as the reboot is complete.
Regards,
Evgheni Dereveanchin
7 years, 9 months
strange score from gerrit-hooks
by Francesco Romani
Hi Infra,
I cannot parse this reason for gerrit hooks:
Check TM::#1414626::OK, found clone candidate ovirt-4.0.zfor target
milestone: ovirt-4.0.6 (-1)
Example: https://gerrit.ovirt.org/#/c/71716/
could anyone please explain the line above and the reason for the score?
Bests,
--
Francesco Romani
Red Hat Engineering Virtualization R & D
IRC: fromani
7 years, 9 months
[JIRA] (OVIRT-1109) Create jobs parameter in manual system tests
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1109?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1109:
--------------------------------
Description:
You should do that by adding a dynamic parameter that'll have a groovy script such as:
{code}
import jenkins.model.*
def list = []
def matchedJobs = Jenkins.instance.items.findAll { job ->
job.name =~ /build-artifacts/
}
matchedJobs.each { job ->
if (!job.name.contains("archived_for_deletion")) {
list << job.name.split('_')[0]
}
}
return list.unique()
{code}
With the above script you'll have all project names. From the project name and the other parameters you can build any job's name:
{code}
{project}_{ovirt_version}_build-artifacts-{distro}-{arch}
{code}
was:
You should do that by adding a dynamic parameter that'll have a groovy script such as:
{code}
import jenkins.model.*
def list = []
def matchedJobs = Jenkins.instance.items.findAll { job ->
job.name =~ /build-artifacts/
}
matchedJobs.each { job ->
if (!job.name.contains("archived_for_deletion")) {
list << job.name.split('_')[0]
}
}
return list.unique()
{code}
With the above script you'll have all project names. From the project name and the other parameters you can build any job's name:
{project}_{ovirt_version}_build-artifacts-{distro}-{arch}
> Create jobs parameter in manual system tests
> --------------------------------------------
>
> Key: OVIRT-1109
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1109
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Reporter: Gil Shinar
> Assignee: infra
>
> You should do that by adding a dynamic parameter that'll have a groovy script such as:
> {code}
> import jenkins.model.*
> def list = []
> def matchedJobs = Jenkins.instance.items.findAll { job ->
> job.name =~ /build-artifacts/
> }
> matchedJobs.each { job ->
> if (!job.name.contains("archived_for_deletion")) {
> list << job.name.split('_')[0]
> }
> }
> return list.unique()
> {code}
> With the above script you'll have all project names. From the project name and the other parameters you can build any job's name:
> {code}
> {project}_{ovirt_version}_build-artifacts-{distro}-{arch}
> {code}
--
This message was sent by Atlassian JIRA
(v1000.718.6#100026)
7 years, 9 months