[JIRA] (OVIRT-2029) Add cache pre-seed functionality to JJB

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2029: Epic Link: OVIRT-400 > Add cache pre-seed functionality to JJB > -

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 642 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64/642/ Build Number: 642 Build Status: Still Failing Triggered By: Started by timer --

[JIRA] (OVIRT-2029) Add cache pre-seed functionality to JJB

Barak Korren created OVIRT-2029: --- Summary: Add cache pre-seed functionality to JJB Key: OVIRT-2029 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2029 Project: oVirt - virtualization made easy

[JIRA] (OVIRT-2030) Add cache-based deletion option to JJB

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2030: Epic Link: OVIRT-400 > Add cache-based deletion option to JJB > --

[JIRA] (OVIRT-2030) Add cache-based deletion option to JJB

Barak Korren created OVIRT-2030: --- Summary: Add cache-based deletion option to JJB Key: OVIRT-2030 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2030 Project: oVirt - virtualization made easy

[JIRA] (OVIRT-2029) Add cache pre-seed functionality to JJB

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2029: Issue Type: Improvement (was: Task) > Add cache pre-seed functionality to JJB > -

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 216 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/216/ Build Number: 216 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last Su

[JIRA] (OVIRT-2031) Use the systemd-nspawn mode for mock

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2031: Epic Link: OVIRT-400 > Use the systemd-nspawn mode for mock >

[JIRA] (OVIRT-2031) Use the systemd-nspawn mode for mock

Barak Korren created OVIRT-2031: --- Summary: Use the systemd-nspawn mode for mock Key: OVIRT-2031 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2031 Project: oVirt - virtualization made easy

[CQ]: 91277, 2 (ovirt-engine-api-model) failed "ovirt-master" system tests

Change 91277,2 (ovirt-engine-api-model) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further det

[JIRA] (OVIRT-2032) Mounting device files prevents using systemd-nspawn in mock

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2032: Epic Link: OVIRT-400 > Mounting device files prevents using systemd-nspawn in mock > -

[JIRA] (OVIRT-2032) Mounting device files prevents using systemd-nspawn in mock

Barak Korren created OVIRT-2032: --- Summary: Mounting device files prevents using systemd-nspawn in mock Key: OVIRT-2032 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2032 Project: oVirt - virtualiza

[JIRA] (OVIRT-2032) Mounting device files prevents using systemd-nspawn in mock

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36587#comment-36587 ] Barak Korren commented on OVIRT-2032: - Issue [#87|https://github.com/rpm-software-manageme

[JIRA] (OVIRT-2032) Mounting device files prevents using systemd-nspawn in mock

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2032: Labels: upstream-issue (was: ) > Mounting device files prevents using systemd-nspawn in mock > --

[oVirt Jenkins] ovirt-node-ng_4.1_build-artifacts-el7-x86_64 - Build # 72 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_4.1_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_4.1_build-artifacts-el7-x86_64/72/ Build Number: 72 Build Status: Still Failing Triggered By: Started by timer - Changes Sin

Change in ds-jenkins-stg[master]: Updated US source to: 28865d2 testing asdf

>From Daniel Belenky : Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/155 ) Change subject: Updated US source to: 28865d2 testing asdf .. Patch Set 1: ci test please -- To view, vi

[JIRA] (OVIRT-2033) Provide a "tagging" mecahnism for transactional mirrors.

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2033: Epic Link: OVIRT-400 > Provide a "tagging" mecahnism for transactional mirrors. >

[JIRA] (OVIRT-2033) Provide a "tagging" mecahnism for transactional mirrors.

Barak Korren created OVIRT-2033: --- Summary: Provide a "tagging" mecahnism for transactional mirrors. Key: OVIRT-2033 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2033 Project: oVirt - virtualization

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 217 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/217/ Build Number: 217 Build Status: Fixed Triggered By: Started by user Marcin Mirecki - Changes Since L

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 215 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/215/ Build Number: 215 Build Status: Fixed Triggered By: Started by user Marcin Mirecki - Changes Since Last Su

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 1 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/1/ Build Number: 1 Build Status: Failure Triggered By: Started by user Gal Ben Haim - Changes Sin

[JIRA] (OVIRT-2034) Recreate the transactional CI mirrors with Pulp

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2034: Epic Link: OVIRT-403 > Recreate the transactional CI mirrors with Pulp > -

[JIRA] (OVIRT-2034) Recreate the transactional CI mirrors with Pulp

Barak Korren created OVIRT-2034: --- Summary: Recreate the transactional CI mirrors with Pulp Key: OVIRT-2034 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2034 Project: oVirt - virtualization made eas

Re: Tried to build WildFly for FC28

On Wed, May 16, 2018 at 1:09 PM, Barak Korren wrote: > > > On 16 May 2018 at 14:03, Martin Perina wrote: > >> Hi, >> >> I've tried to rebuild WildFly package for FC28 [1], but the build [2] >> failed on: >> >> *10:37:56* ERROR: Command failed: *10:37:56* # /usr/bin/yum --installroot >> /var/li

[JIRA] (OVIRT-2035) CQ failed due to a patch from a non-whitelisted email

Evgheni Dereveanchin created OVIRT-2035: --- Summary: CQ failed due to a patch from a non-whitelisted email Key: OVIRT-2035 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2035 Project: oVirt -

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 175 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/175/ Build Number: 175 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last Succes

[JIRA] (OVIRT-2035) CQ failed due to a patch from a non-whitelisted email

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2035: Epic Link: OVIRT-400 > CQ failed due to a patch from a non-whitelisted email > --

[JIRA] (OVIRT-2035) CQ failed due to a patch from a non-whitelisted email

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-2035: Epic Link: OVIRT-400 > CQ failed due to a patch from a non-whitelisted email > --

[JIRA] (OVIRT-2035) CQ failed due to a patch from a non-whitelisted email

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36591#comment-36591 ] Barak Korren commented on OVIRT-2035: - Hmm... I think we fixed this in V2 - its a bit tric

[JIRA] (OVIRT-2035) CQ failed due to a patch from a non-whitelisted email

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren reassigned OVIRT-2035: --- Assignee: Barak Korren (was: infra) > CQ failed due to a patch from a non-whitelisted emai

[CQ]: 91312,1 (ovirt-host) failed "ovirt-master" system tests

Change 91312,1 (ovirt-host) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about t

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 2 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/2/ Build Number: 2 Build Status: Still Failing Triggered By: Started by user Gal Ben Haim - Chang

Re: Tried to build WildFly for FC28

On 17 May 2018 at 12:49, Martin Perina wrote: > > > On Wed, May 16, 2018 at 1:09 PM, Barak Korren wrote: > >> >> >> On 16 May 2018 at 14:03, Martin Perina wrote: >> >>> Hi, >>> >>> I've tried to rebuild WildFly package for FC28 [1], but the build [2] >>> failed on: >>> >>> *10:37:56* ERROR: Com

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 3 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/3/ Build Number: 3 Build Status: Still Failing Triggered By: Started by user Gal Ben Haim - Chang

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 4 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/4/ Build Number: 4 Build Status: Still Failing Triggered By: Started by user Gal Ben Haim - Chang

[CQ]: 91320,1 (ovirt-host) failed "ovirt-4.2" system tests

Change 91320,1 (ovirt-host) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 5 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/5/ Build Number: 5 Build Status: Still Failing Triggered By: Started by user Gal Ben Haim - Chang

[JIRA] (OVIRT-2036) Post merge patchsets can run on pre-merge jobs in STDCI V2

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Belenky updated OVIRT-2036: -- Epic Link: OVIRT-400 > Post merge patchsets can run on pre-merge jobs in STDCI V2 > --

[JIRA] (OVIRT-2036) Post merge patchsets can run on pre-merge jobs in STDCI V2

Daniel Belenky created OVIRT-2036: - Summary: Post merge patchsets can run on pre-merge jobs in STDCI V2 Key: OVIRT-2036 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2036 Project: oVirt - virtuali

Re: Tried to build WildFly for FC28

On Thu, May 17, 2018 at 1:00 PM, Barak Korren wrote: > > > On 17 May 2018 at 12:49, Martin Perina wrote: > >> >> >> On Wed, May 16, 2018 at 1:09 PM, Barak Korren wrote: >> >>> >>> >>> On 16 May 2018 at 14:03, Martin Perina wrote: >>> Hi, I've tried to rebuild WildFly package for

[JIRA] (OVIRT-2037) Patchsets from non-whitelisted users can't run post-merge tasks

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Belenky updated OVIRT-2037: -- Epic Link: OVIRT-400 > Patchsets from non-whitelisted users can't run post-merge tasks > -

[JIRA] (OVIRT-2036) Pre-merged patchsets can run on post-merged jobs in STDCI V2

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Belenky updated OVIRT-2036: -- Summary: Pre-merged patchsets can run on post-merged jobs in STDCI V2 (was: Post merge patchs

[JIRA] (OVIRT-2036) Pre-merged patchsets can run on post-merged jobs in STDCI V2

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Belenky updated OVIRT-2036: -- Description: Currently, if one comments 'ci re-merge please' on a pre-merged patch, STDCI V2

[JIRA] (OVIRT-2037) Patchsets from non-whitelisted users can't run post-merge tasks

Daniel Belenky created OVIRT-2037: - Summary: Patchsets from non-whitelisted users can't run post-merge tasks Key: OVIRT-2037 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2037 Project: oVirt - vi

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 6 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/6/ Build Number: 6 Build Status: Still Failing Triggered By: Started by timer - Changes Since Las

[CQ]: 91215,1 (vdsm) failed "ovirt-4.2" system tests

Change 91215,1 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change

[JIRA] (OVIRT-2034) Recreate the transactional CI mirrors with Pulp

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36593#comment-36593 ] Barak Korren commented on OVIRT-2034: - One very important concept for implementing the mir

[CQ]: 91311, 2 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 91311,2 (ovirt-host) failed. However, this change seems not to be the root cause for this failure. Change 91312,1 (ovirt-host) that this change depends on or is based on, was detected as the cause of the testing failures. Th

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 7 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/7/ Build Number: 7 Build Status: Still Failing Triggered By: Started by user Gal Ben Haim - Chang

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 393 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/393/ Build Number: 393 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success

[oVirt CI] standard-enqueue - Build #13529 - FAILURE!

Build: http://jenkins.ovirt.org/job/standard-enqueue/13529/ Build Name: #13529 Build Description: Gerrit: 91337 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91337 - title: packaging: setup: postgres95: Pass locale - project: ovirt-engine - branch: ovirt-engin

[oVirt CI] standard-enqueue - Build #13530 - FAILURE!

Build: http://jenkins.ovirt.org/job/standard-enqueue/13530/ Build Name: #13530 Build Description: Gerrit: 91336 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91336 - title: Revert \"packaging: setup: postgres95: Pass locale\" - project: ovirt-engine - branch:

[CQ]: 90647, 8 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 90647,8 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 91221,3 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change ha

Re: [CQ]: 91311, 2 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause

2018-05-17 14:58 GMT+02:00 oVirt Jenkins : > A system test invoked by the "ovirt-master" change queue including change > 91311,2 (ovirt-host) failed. However, this change seems not to be the root > cause for this failure. Change 91312,1 (ovirt-host) that this change > depends on > or is based on,

[oVirt Jenkins] ovirt-appliance_4.1_build-artifacts-el7-x86_64 - Build # 72 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-appliance_4.1_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_4.1_build-artifacts-el7-x86_64/72/ Build Number: 72 Build Status: Still Failing Triggered By: Started by timer - Changes

[CQ]: 91249, 7 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 91249,7 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 91221,3 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change ha

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 176 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/176/ Build Number: 176 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success: -

[CQ]: 91133, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 91133,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 91221,3 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change ha

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 8 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/8/ Build Number: 8 Build Status: Still Failing Triggered By: Started by user Gal Ben Haim - Chang

Change in barak-test[master]: jenkins integ test

>From Evgheni Dereveanchin : Evgheni Dereveanchin has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/17 ) Change subject: jenkins integ test .. Patch Set 1: Code-Review+1 test comment after gerrit upgr

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 9 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/9/ Build Number: 9 Build Status: Still Failing Triggered By: Started by timer - Changes Since Las

[JIRA] (OVIRT-2028) Re: [Infra-private] Please remove yklei...@redhat.com from infra@ovirt.org

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-2028: --- Assignee: Evgheni Dereveanchin (was: infra) > Re: [Infra-private] Please r

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 152 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifacts-el7-x86_64/152/ Build Number: 152 Build Status: Still Failing Triggered By: Started by timer --

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1493

See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 177 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/177/ Build Number: 177 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success: ---

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 10 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/10/ Build Number: 10 Build Status: Still Failing Triggered By: Started by timer - Changes Since L

Jenkins build is back to normal : system-sync_mirrors-epel-el6-x86_64 #1494

See ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64 - Build # 534 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64/534/ Build Number: 534 Build Status: Still Failing Triggered By: Started by timer --