[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by eedri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jir... ]
eedri commented on OVIRT-1500:
------------------------------
[~mureinik] how often are you hitting this issue?
If we will enable Jenkins jobs to run also on changes w/o 'code change' it might have a significant impact on the CI resources and potentially increase the number of jobs running on CI ( w/o a real code change ) and will result in longer waiting time per job.
> CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
> -------------------------------------------------------------------
>
> Key: OVIRT-1500
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Gerrit/git, oVirt CI
> Reporter: Allon Mureinik
> Assignee: infra
>
> In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit.
> Looking through gerrit's history, here's what I *think* is going on:
> 08:41 - patchset #1 is submitted
> 08:41 - CI (check-patch) starts for both EL7 and fc25
> _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_
> 08:42 - patchset #2 is submitted
> _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_
> 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason.
> Expected behavior:
> If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited.
--
This message was sent by Atlassian JIRA
(v1000.1092.1#100053)
7 years, 4 months
[JIRA] (OVIRT-682) Improve CI logging
by eedri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira... ]
eedri updated OVIRT-682:
------------------------
Priority: Low (was: Medium)
> Improve CI logging
> ------------------
>
> 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.1092.1#100053)
7 years, 4 months
[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure
by eedri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-713?page=com.atlassian.jira... ]
eedri commented on OVIRT-713:
-----------------------------
[~gbenhaim@redhat.com][~ngoldin(a)redhat.com] was there any progress on this? if we still suffer from reposync errors, might worth prioritizing.
> Clean reposync directory after n times of sync failure
> ------------------------------------------------------
>
> Key: OVIRT-713
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: Gal Ben Haim
> Assignee: infra
>
> Sometimes reposync fail to sync rpms that already been synced.
> To resolve this issue, lago removes those rpms, and runs reposync again.
> This resolution doesn't always work, and then we need to clean all the rpms that were synced.
> We want lago to clear the cached rpms after n times of sync failure, and then try to sync again.
--
This message was sent by Atlassian JIRA
(v1000.1092.1#100053)
7 years, 4 months