December 2017 - Infra - Ovirt List Archives

[vdsm][tag][ovirt-4.2.0] Vdsm tagged: v4.20.9.2

by Francesco Romani

Hi infra, we have a new Vdsm tag on branch ovirt-4.2.0 for oVirt 4.2.0: Tagger: Francesco Romani <fromani(a)redhat.com> Date: Wed Dec 13 11:18:00 2017 +0100 Vdsm 4.20.9.2 for oVirt 4.2.0 RC 3 commit 66a4b54e94d786740f758befd0d907f1b569bc44 +++ NOTE ABOUT BRANCHING: * We are merging again patches targeted for 4.2.1 on master * I created the branch ovirt-4.2.0 to collect the fixes needed for the release 4.2.0. Only GA blockers are allowed in. * We don't yet have plans to branch out ovirt-4.2.0 from master. Following the usual Vdsm habit, we will branch out late, *after* Engine does. Bests, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

7 years

1
0
0 / 0

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

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 84945,8 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 85147,4 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85147,4 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84945/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85147/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4380/

7 years

1
0
0 / 0

OST Networking suite -- artifacts aren't collected.

by Leon Goldberg

Hey guys, I have a weird problem with our new OST suite. Although I copy certain directories to ../ovirt-system-tests/exported-artifacts (i.e. root dir/exported-artifacts), they are not being collected. Running the suite via mock, I can see that the directory is present with the logs (plus some other files/directories), however in CI they are not. I've tried running both run_suite.sh and check-patch.sh. Locally I see the artifacts in both. Here's the patch [1]. It's unfinished work. I am familiar with lago's abstraction, and although is super ugly, the relative path in _collect_artifacts seems correct. Thanks for any help! [1] https://gerrit.ovirt.org/#/c/84567/

7 years

2
3
0 / 0

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

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 84868,11 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 85147,4 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85147,4 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84868/11 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85147/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4378/

7 years

1
0
0 / 0

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

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 85317,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 85147,4 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85147,4 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/85317/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85147/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4374/

7 years

1
0
0 / 0

Fwd: [Test-Announce] Fedora 25 End Of Life

by Sandro Bonazzola

FYI ---------- Messaggio inoltrato ---------- Da: "Mohan Boddu" <mboddu(a)redhat.com> Data: 12 Dic 2017 21:41 Oggetto: [Test-Announce] Fedora 25 End Of Life A: <announce(a)lists.fedoraproject.org>, < devel-announce(a)lists.fedoraproject.org>, < test-announce(a)lists.fedoraproject.org> Cc: As of the 12th of December 2017, Fedora 25 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 25. Fedora 26 will continue to receive updates until approximately one month after the release of Fedora 28. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Mohan Boddu. [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle# Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades _______________________________________________ test-announce mailing list -- test-announce(a)lists.fedoraproject.org To unsubscribe send an email to test-announce-leave(a)lists.fedoraproject.org _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org

7 years

1
0
0 / 0

[CQ]: 85147,4 (vdsm) failed "ovirt-master" system tests

by oVirt Jenkins

Change 85147,4 (vdsm) 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 the change see: https://gerrit.ovirt.org/#/c/85147/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4371/

7 years

1
0
0 / 0

[CQ]: 85321, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests

by oVirt Jenkins

Change 85321,1 (ovirt-provider-ovn) 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 the change see: https://gerrit.ovirt.org/#/c/85321/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4366/

7 years

1
0
0 / 0

Change in us-jenkins-stg2[master]: Making a code change to sync to DS

by review＠gerrit-staging.phx.ovirt.org

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has submitted this change and it was merged. ( https://gerrit-staging.phx.ovirt.org/107 ) Change subject: Making a code change to sync to DS ...................................................................... Making a code change to sync to DS Change-Id: I53265716340611a7466e44180972ea16106220b9 --- M upstream-file1.txt 1 file changed, 1 insertion(+), 1 deletion(-) Approvals: Jenkins CI: Passed CI tests Barak Korren: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/107 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-MessageType: merged Gerrit-Change-Id: I53265716340611a7466e44180972ea16106220b9 Gerrit-Change-Number: 107 Gerrit-PatchSet: 1 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

7 years

1
0
0 / 0

Change in us-jenkins-stg2[master]: Making a code change to sync to DS

by review＠gerrit-staging.phx.ovirt.org

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/107 ) Change subject: Making a code change to sync to DS ...................................................................... Patch Set 1: Verified+1 Code-Review+2 Continuous-Integration+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/107 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I53265716340611a7466e44180972ea16106220b9 Gerrit-Change-Number: 107 Gerrit-PatchSet: 1 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Tue, 12 Dec 2017 13:14:17 +0000 Gerrit-HasComments: No

7 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra December 2017