10:58 a.m.
[
https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira...
]
Barak Korren edited comment on OVIRT-682 at 2/26/17 11:58 AM:
--------------------------------------------------------------
We can probably improve the user experience by putting a better message in Gerrit,
something like:
{quote}
You can see standard-CI script output log +here(1)+
For individual test results please +click here(2)+, or use the +test results analyser(3)+
Additional built artifacts can be found +here(4)+
For full, unfiltered, job output +click here(5)+
To re-trigger the job +click here(6)+ or type *\@ci check*
{quote}
Where:
* (1) points to the {{check-patch.sh}}, {check-merged.sh}}, etc. script output.
* If any JUNIT XML files were found (If not the line shouldnt be shown):
** (2) points to the test results page
** (3) point to the test results analyser
* If any artifacts that are not mock logs or JUNIT XML files wee found (4) points to them.
If <= 3 artifacts found we may even include direct links (This will be useful for
things like {{differences.html}} in the Jenkins repo.
* (5) Will point to the good-old job console output screen
* If the job failed, (6) will point to the re-trigger button
We will need to check if its possible to embed links in Gerrit comments. If no we will
unfortunately have to use ugly full URLs.
was (Author: bkorren(a)redhat.com):
We can probably improve the user experience by putting a better message in Gerrit,
something like:
{quote}
You can see standard-CI script output log +here(1)+
For individual test results please +click here(2)+, or use the +test results analyser(3)+
Additional built artifacts can be found +here(4)+
For full, unfiltered, job output +click here(5)+
{quote}
Where:
* (1) points to the {{check-patch.sh}}, {check-merged.sh}}, etc. script output.
* If any JUNIT XML files were found (If not the line shouldnt be shown):
** (2) points to the test results page
** (3) point to the test results analyser
* If any artifacts that are not mock logs or JUNIT XML files wee found (4) points to them.
If <= 3 artifacts found we may even include direct links (This will be useful for
things like {{differences.html}} in the Jenkins repo.
* (5) Will point to the good-old job console output screen
We will need to check if its possible to embed links in Gerrit comments. If no we will
unfortunately have to use ugly full URLs.
Improve CI logging
------------------
Key: OVIRT-682
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: eyal edri [Administrator]
Assignee: infra
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.784.2#100032)
2921
days inactive
2921
days old
0 comments
1 participants
participants (1)
-
Barak Korren (oVirt JIRA)