[
https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira...
]
Barak Korren commented on OVIRT-682:
------------------------------------
Gerrit trigger feedback configuration is not flexible enough to let us have each job
customize the output it sends to Gerrit.
Instead we will need to send the results to Gerrit ourselves with something like the
GerritServer object (See [Gerrit
74874|https://gerrit.ovirt.org/#/c/74874/]). But when
sending results, the Gerrit trigger also calculates the votes for the flags by looking at
all the jobs that it invoked. To do this ourselves we will need to be able to track all
the checking scripts that are running in parallel for a given patchset, this probably
means we have to implement OVIRT-1522 first.
Improve CI logging and reporting to Gerrit (v2)
-----------------------------------------------
Key: OVIRT-682
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-682
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: eedri
Assignee: infra
Priority: Low
Labels: standard-ci
On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
> Hi all,
>
> Lately vdsm builds are failing in the install packages stage with
> this unhelpful error:
>
> 13:59:42 INFO: installing package(s): autoconf automake gdb ...
> 13:59:53 ERROR: Command failed. See logs for output.
>
> I downloaded the logs.tgz file from
>
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-
> x86_64/1154/artifact/exported-artifacts/logs.tgz
>
> And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/
> root.log
> I found found this error:
>
> DEBUG util.py:421: Error: Package:
> python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch
> (ovirt-snapshot)
> DEBUG util.py:421: Requires: ioprocess =
> 0.17.0-1.201608111609.gitbd272f2.fc24
> DEBUG util.py:421: Available:
> ioprocess-0.15.1-1.fc24.x86_64 (fedora)
> DEBUG util.py:421: ioprocess = 0.15.1-1.fc24
> DEBUG util.py:421: Available:
> ioprocess-0.16.1-1.fc24.x86_64 (updates)
> DEBUG util.py:421: ioprocess = 0.16.1-1.fc24
> DEBUG util.py:421: Available:
> ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64
> (ovirt-snapshot)
> DEBUG util.py:421: ioprocess =
> 0.17.0-1.201607121058.gitbd272f2.fc24
> DEBUG util.py:421: Available:
> ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64
> (ovirt-snapshot)
> DEBUG util.py:421: ioprocess =
> 0.17.0-1.201608111129.gitbd272f2.fc24
>
> So we have 2 issues here:
>
> 1. We need *all* errors in the console
>
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-
> x86_64/1154/console
Not sure its possible or easy to do, these errors usually come from mock
and are not relevant to the code running on the console.
I've cc'd infra-support and updated topic to track it and check our options.
Going foward, we might want to install a log collector like logstash and
then searching errors there should be much easier.
>
>
> 2. Someone need to fix the ovirt-snapshot repository - it should have
> the missing ioprocess
> package.
> Maybe the project xml is not correct?
>
> Nir
>
--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian JIRA
(v1000.1112.0#100055)