oVirt infra daily report - unstable production jobs - 243
by jenkins＠jenkins.phx.ovirt.org
------=_Part_23_881821720.1488150008806
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/243//artifact/exported...
Cheers,
Jenkins
------=_Part_23_881821720.1488150008806
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 - 26/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_4.1_hc-system-tests/">ovirt_4.1_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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/">ovirt_4.1_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_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;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_el7_merged/">repos_4.1_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_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_23_881821720.1488150008806--
7 years, 1 month
[JIRA] (OVIRT-1097) review ovirt snapshot static repos and remove not needed RPMs
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1097?page=com.atlassian.jir... ]
eyal edri [Administrator] updated OVIRT-1097:
---------------------------------------------
Status: To Do (was: In Progress)
> review ovirt snapshot static repos and remove not needed RPMs
> -------------------------------------------------------------
>
> Key: OVIRT-1097
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1097
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Reporter: eyal edri [Administrator]
> Assignee: infra
>
> We should aim to drop the static repos, any RPMs oVirt needs should come from one of the following sources:
> 1. Built in standard CI via build artifacts job
> 2. If its external, then we need to use the origin repo and not copy it to be on oVirt.
> We can start from master and move to stable versions when its verified.
> existing RPMS on master static: (showing el7 as most OS should be similar )
> .
> ├── noarch
> │ ├── ebay-cors-filter-1.0.1-3.el7.noarch.rpm
> │ ├── ebay-cors-filter-javadoc-1.0.1-3.el7.noarch.rpm
> │ ├── nsis-simple-service-plugin-1.30-1.noarch.rpm
> │ ├── openvswitch-selinux-policy-2.6.90-1.el7.centos.noarch.rpm
> │ ├── openvswitch-test-2.6.90-1.el7.centos.noarch.rpm
> │ ├── ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch.rpm
> │ ├── python-openvswitch-2.6.90-1.el7.centos.noarch.rpm
> │ ├── rubygem-fluent-plugin-rewrite-tag-filter-1.5.5-1.el7.centos.noarch.rpm
> │ └── rubygem-fluent-plugin-rewrite-tag-filter-doc-1.5.5-1.el7.centos.noarch.rpm
> ├── ppc64
> │ ├── python-cpopen-1.3-4.el7.ppc64.rpm
> │ └── python-cpopen-debuginfo-1.3-4.el7.ppc64.rpm
> ├── ppc64le
> ├── repodata
> │ ├── 008d859bb942a115e9b0077bd65c84f49e5a01eca2209ad393c27a036237783f-filelists.xml.gz
> │ ├── 14a142882a77ec4120c34a7d88dd69bdcf9463915c34d0f139fe6a9f01a78ca5-filelists.sqlite.bz2
> │ ├── 3299fdf213c4ee0e8bea41142691d1ab861496291a2302dfa32a7247eb43660c-primary.xml.gz
> │ ├── 648a0a77bce1ba70babe4c8f5ac90b8f4b89103f8fa429903d572022066367be-primary.sqlite.bz2
> │ ├── 715d2c608d40b1982b5a02c1c98bc6fca827e46d260849afc8eec6ad928caa6f-other.xml.gz
> │ ├── f54bf13a0e486128a9bc41a975e4ecf597b553c47a7cdb70c169ce8c042c3b94-other.sqlite.bz2
> │ └── repomd.xml
> ├── SRPMS
> │ ├── ebay-cors-filter-1.0.1-3.el7.src.rpm
> │ ├── nsis-simple-service-plugin-1.30-1.src.rpm
> │ ├── openvswitch-2.6.90-1.el7.centos.src.rpm
> │ ├── ovirt-engine-wildfly-10.1.0-1.el7.src.rpm
> │ ├── ovirt-engine-wildfly-overlay-10.0.0-1.el7.src.rpm
> │ ├── ovirt-web-ui-0.1.0-4.el7.centos.src.rpm
> │ ├── ovirt-web-ui-0.1.1-2.el7.centos.src.rpm
> │ ├── repodata
> │ │ ├── 1f13684ed34daa19755884e49132dcee7b60eafd38b52a51f945a92e63459e65-filelists.xml.gz
> │ │ ├── 3f20e34cc666f1df8667288b5cdf3eb449fed6ab8b032e1a0d9be0fc78d53b56-primary.sqlite.bz2
> │ │ ├── 7e260234efc35f032a0d22f976d17758b28555566d742c04911a4758c3552db1-primary.xml.gz
> │ │ ├── 87cdc086330908e1dc39ca53c50eb9b6ba3627b2b562e0d278a0e899fd925167-other.xml.gz
> │ │ ├── e2cb0de1abd9d51f783862d7d498ead766a96261dd942230f0182afee7195bdb-other.sqlite.bz2
> │ │ ├── ed15cb166756bbf49aecd3f8e65ca0da96ca860d64e4fc80a141280a9114e5ee-filelists.sqlite.bz2
> │ │ └── repomd.xml
> │ ├── rubygem-fluent-plugin-rewrite-tag-filter-1.5.5-1.el7.centos.src.rpm
> │ └── vhostmd-0.5-11.el7.src.rpm
> └── x86_64
> ├── openvswitch-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-debuginfo-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-devel-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-central-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-common-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-docker-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-host-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-vtep-2.6.90-1.el7.centos.x86_64.rpm
> ├── ovirt-engine-wildfly-10.1.0-1.el7.x86_64.rpm
> ├── ovirt-web-ui-0.1.0-4.el7.centos.x86_64.rpm
> ├── ovirt-web-ui-0.1.1-2.el7.centos.x86_64.rpm
> ├── vhostmd-0.5-11.el7.x86_64.rpm
> ├── vhostmd-debuginfo-0.5-11.el7.x86_64.rpm
> ├── vm-dump-metrics-0.5-11.el7.x86_64.rpm
> └── vm-dump-metrics-devel-0.5-11.el7.x86_64.rpm
--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
7 years, 1 month
[JIRA] (OVIRT-1193) add on request 'ci help' command via Gerrit
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jir... ]
eyal edri [Administrator] commented on OVIRT-1193:
--------------------------------------------------
I still think its worth asking the developers again, proposing the relevant options, after all it was their request as you say.
Also, one or two developers might have different ideas then the majority, so we'll need an agreement on one suggestion from the majority.
> add on request 'ci help' command via Gerrit
> -------------------------------------------
>
> Key: OVIRT-1193
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Components: Gerrit/git
> Reporter: Barak Korren
> Assignee: infra
>
> On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote:
> > Hi,
> >
> > do you think it would make sense to send a copy-and-paste ready
> > message with help to every new gerrit change?
> >
> > It could provide all the system test (lago) links, mention the Rerun
> > hooks syntax and so on. Just so we do not have to search for it all
> > the time?
> This is doable, but I think experienced users may find this annoying
> it ifs too long.
> I'm thinking it may be better to have such a message just suggesting
> to type something like '@ci help' to get the full help.
> It may even be possible to make it clickable with some trickery rather
> then just copy-and-paster ready (I will need to check if its possible
> to inject links into Gerrit comments).
> Apart from that, Roy offered to write a Gerrit plugin that will add
> buttons with the various CI commands.
> Adding infra-support to get a Jira ticket opened.
> --
> Barak Korren
> bkorren(a)redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
7 years, 1 month
[JIRA] (OVIRT-1193) add on request 'ci help' command via Gerrit
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1193:
-------------------------------------
I think top of gerrit or the 1st comment in gerrit are visually equivalent, with the difference that the 1st comment is easier to implement atm...
WRT to developer survey - remember that the suggestion for this came from the developers...
> add on request 'ci help' command via Gerrit
> -------------------------------------------
>
> Key: OVIRT-1193
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Components: Gerrit/git
> Reporter: Barak Korren
> Assignee: infra
>
> On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote:
> > Hi,
> >
> > do you think it would make sense to send a copy-and-paste ready
> > message with help to every new gerrit change?
> >
> > It could provide all the system test (lago) links, mention the Rerun
> > hooks syntax and so on. Just so we do not have to search for it all
> > the time?
> This is doable, but I think experienced users may find this annoying
> it ifs too long.
> I'm thinking it may be better to have such a message just suggesting
> to type something like '@ci help' to get the full help.
> It may even be possible to make it clickable with some trickery rather
> then just copy-and-paster ready (I will need to check if its possible
> to inject links into Gerrit comments).
> Apart from that, Roy offered to write a Gerrit plugin that will add
> buttons with the various CI commands.
> Adding infra-support to get a Jira ticket opened.
> --
> Barak Korren
> bkorren(a)redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
7 years, 1 month
[JIRA] (OVIRT-1193) add on request 'ci help' command via Gerrit
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jir... ]
eyal edri [Administrator] commented on OVIRT-1193:
--------------------------------------------------
Another option is to add it to the top of the Gerrit as part of the layout.
But anyhow, I think its best to do a short survey on the devel list before implementing this.
> add on request 'ci help' command via Gerrit
> -------------------------------------------
>
> Key: OVIRT-1193
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Components: Gerrit/git
> Reporter: Barak Korren
> Assignee: infra
>
> On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote:
> > Hi,
> >
> > do you think it would make sense to send a copy-and-paste ready
> > message with help to every new gerrit change?
> >
> > It could provide all the system test (lago) links, mention the Rerun
> > hooks syntax and so on. Just so we do not have to search for it all
> > the time?
> This is doable, but I think experienced users may find this annoying
> it ifs too long.
> I'm thinking it may be better to have such a message just suggesting
> to type something like '@ci help' to get the full help.
> It may even be possible to make it clickable with some trickery rather
> then just copy-and-paster ready (I will need to check if its possible
> to inject links into Gerrit comments).
> Apart from that, Roy offered to write a Gerrit plugin that will add
> buttons with the various CI commands.
> Adding infra-support to get a Jira ticket opened.
> --
> Barak Korren
> bkorren(a)redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
7 years, 1 month
[JIRA] (OVIRT-1193) add on request 'ci help' command via Gerrit
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1193:
-------------------------------------
The thing is - if last week's events taught us anything is that people are not willing to remember anything - not even one command.
I thing that a short enough message, that will appear once and only once when a patch (patch! not patchset!) is created, is unobtrusive enough to not be annoying. The huge benefit of this is that now no one can say he never heard that there is a CI system and it has commands.
This will also be a good place to warn new contributors about not being in the whitelist and tell them what to do.
> add on request 'ci help' command via Gerrit
> -------------------------------------------
>
> Key: OVIRT-1193
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Components: Gerrit/git
> Reporter: Barak Korren
> Assignee: infra
>
> On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote:
> > Hi,
> >
> > do you think it would make sense to send a copy-and-paste ready
> > message with help to every new gerrit change?
> >
> > It could provide all the system test (lago) links, mention the Rerun
> > hooks syntax and so on. Just so we do not have to search for it all
> > the time?
> This is doable, but I think experienced users may find this annoying
> it ifs too long.
> I'm thinking it may be better to have such a message just suggesting
> to type something like '@ci help' to get the full help.
> It may even be possible to make it clickable with some trickery rather
> then just copy-and-paster ready (I will need to check if its possible
> to inject links into Gerrit comments).
> Apart from that, Roy offered to write a Gerrit plugin that will add
> buttons with the various CI commands.
> Adding infra-support to get a Jira ticket opened.
> --
> Barak Korren
> bkorren(a)redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
7 years, 1 month
[JIRA] (OVIRT-1193) add on request 'ci help' command via Gerrit
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jir... ]
eyal edri [Administrator] edited comment on OVIRT-1193 at 2/26/17 6:19 PM:
---------------------------------------------------------------------------
I think people will be annoyed by that, it willl spam the comments in all patches.
I think it makes sense to developers to know one command - 'ci please help' e.g., and we need to add it to the signatures of emails from infra to devel, to the Jenkins UI and ovirt site.
So people will only need to remember one command, and once they type it, it will give them info on what is available.
was (Author: eedri):
I think people will be annoyed by that, i'll spam the comments in all patches.
I think it makes sense to developers to know one command - 'ci please help' e.g., and we need to add it to the signatures of emails from infra to devel, to the Jenkins UI and ovirt site.
So people will only need to remember one command, and once they type it, it will give them info on what is available.
> add on request 'ci help' command via Gerrit
> -------------------------------------------
>
> Key: OVIRT-1193
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Components: Gerrit/git
> Reporter: Barak Korren
> Assignee: infra
>
> On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote:
> > Hi,
> >
> > do you think it would make sense to send a copy-and-paste ready
> > message with help to every new gerrit change?
> >
> > It could provide all the system test (lago) links, mention the Rerun
> > hooks syntax and so on. Just so we do not have to search for it all
> > the time?
> This is doable, but I think experienced users may find this annoying
> it ifs too long.
> I'm thinking it may be better to have such a message just suggesting
> to type something like '@ci help' to get the full help.
> It may even be possible to make it clickable with some trickery rather
> then just copy-and-paster ready (I will need to check if its possible
> to inject links into Gerrit comments).
> Apart from that, Roy offered to write a Gerrit plugin that will add
> buttons with the various CI commands.
> Adding infra-support to get a Jira ticket opened.
> --
> Barak Korren
> bkorren(a)redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
7 years, 1 month