Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #50

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

[oVirt Jenkins] ovirt-release_master_build-artifacts-fcraw-x86_64 - Build # 199 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86_64/199/ Build Number: 199 Build Status: Fixed Triggered By: Started by timer -

oVirt infra daily report - unstable production jobs - 909

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

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #49

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

Re: [ovirt-devel] Re: CI: vdsm-standard-check-patch fails

On Tue, Aug 6, 2019 at 5:01 PM Amit Bawer wrote: > > > On Tue, Aug 6, 2019 at 4:58 PM Nir Soffer wrote: > >> On Tue, Aug 6, 2019 at 11:27 AM Amit Bawer wrote: >> >>> I have seen some improvement: when I re-trigger the CI per patch I am >>> able to pass or get the actual test errors if any (if

[CQ]: 375, 3 (stage-stdci2) failed "dummy-master" system tests, but isn't the failure root cause

A system test invoked by the "dummy-master" change queue including change 375,3 (stage-stdci2) failed. However, this change seems not to be the root cause for this failure. Change 310,1 (stage-stdci2) that this change depends on or is based on, was detected as the cause of the testing failures.

Re: [ovirt-devel] Re: CI: vdsm-standard-check-patch fails

On Tue, Aug 6, 2019 at 4:58 PM Nir Soffer wrote: > On Tue, Aug 6, 2019 at 11:27 AM Amit Bawer wrote: > >> I have seen some improvement: when I re-trigger the CI per patch I am >> able to pass or get the actual test errors if any (if not on first try, >> then on second one). >> Probably not a

Re: [ovirt-devel] Re: CI: vdsm-standard-check-patch fails

On Tue, Aug 6, 2019 at 11:27 AM Amit Bawer wrote: > I have seen some improvement: when I re-trigger the CI per patch I am able > to pass or get the actual test errors if any (if not on first try, then on > second one). > Probably not a very useful information, but I have noticed that when I >

[JIRA] (OVIRT-2771) merge ljeli...@redhat.com gerrit accounts

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-2771: --- Assignee: Evgheni Dereveanchin (was: infra) > merge ljeli...@redhat.com

[CQ]: 279, 6 (stage-stdci2) failed "dummy-master" system tests, but isn't the failure root cause

A system test invoked by the "dummy-master" change queue including change 279,6 (stage-stdci2) failed. However, this change seems not to be the root cause for this failure. Change 310,1 (stage-stdci2) that this change depends on or is based on, was detected as the cause of the testing failures.

[CQ]: 279, 6 (stage-stdci2) failed "dummy-master" system tests, but isn't the failure root cause

A system test invoked by the "dummy-master" change queue including change 279,6 (stage-stdci2) failed. However, this change seems not to be the root cause for this failure. Change 310,1 (stage-stdci2) that this change depends on or is based on, was detected as the cause of the testing failures.

[CQ]: 279, 6 (stage-stdci2) failed "dummy-master" system tests, but isn't the failure root cause

A system test invoked by the "dummy-master" change queue including change 279,6 (stage-stdci2) failed. However, this change seems not to be the root cause for this failure. Change 310,1 (stage-stdci2) that this change depends on or is based on, was detected as the cause of the testing failures.

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #48

See Changes: [Barak Korren] mock_configs: Drop proxy use for FCRAW [Gal Ben Haim] check-patch: Don't assume python2 is installed [Barak Korren] standard-pipelines: Add a

[CQ]: 279, 6 (stage-stdci2) failed "dummy-master" system tests, but isn't the failure root cause

A system test invoked by the "dummy-master" change queue including change 279,6 (stage-stdci2) failed. However, this change seems not to be the root cause for this failure. Change 310,1 (stage-stdci2) that this change depends on or is based on, was detected as the cause of the testing failures.

[CQ]: 369,1 (dummy-system-tests) failed "dummy-master" system tests

Change 369,1 (dummy-system-tests) is probably the reason behind recent system test failures in the "dummy-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

Re: [ovirt-devel] CI: vdsm-standard-check-patch fails

I have seen some improvement: when I re-trigger the CI per patch I am able to pass or get the actual test errors if any (if not on first try, then on second one). Probably not a very useful information, but I have noticed that when I push 30+ patches at the same time the AWS connection issue