oVirt infra daily report - unstable production jobs - 241

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/241//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

[JIRA] (OVIRT-1195) Unexplained failure in CI job

Yaniv Kaul created OVIRT-1195: - Summary: Unexplained failure in CI job Key: OVIRT-1195 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1195 Project: oVirt - virtualization made easy Issue

[JIRA] (OVIRT-1195) Unexplained failure in CI job

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1195: -- Epic Link: OVIRT-400 > Unexplained failure in CI job > - > >

Re: [HEADS UP] ovift-engine: repository closure check on check-patch

Sorry, but I really don't think this is the right direction to go. This exposes check-patch to outside repos and may result in repo-stability-related failures after we've made great efforts to eliminate those. This kind of test should really be done at the OST stage IMO. בתאריך 24 בפבר׳ 2017

Re: [HEADS UP] ovift-engine: repository closure check on check-patch

On Fri, Feb 24, 2017 at 4:59 PM, Sandro Bonazzola wrote: > Hi, > with the following commits: > - https://gerrit.ovirt.org/71553 > - https://gerrit.ovirt.org/71623 > > a minimal repository closure check is added to check-patches.sh. > Instead of performing a full blown

[HEADS UP] ovift-engine: repository closure check on check-patch

Hi, with the following commits: - https://gerrit.ovirt.org/71553 - https://gerrit.ovirt.org/71623 a minimal repository closure check is added to check-patches.sh. Instead of performing a full blown repository closure, I limited the check to the built rpms in oreder to reduce the risk of hitting