This mail is to provide the current status of CQ and allow people to review status before and after the weekend.Last failure was on 18-06 for project v2v-conversion-host due to failed build-artifacts
Please refer to below colour map for further information on the meaning of the colours.CQ-4.2: GREEN (#1)which is already fixed by next merged patches.CQ-4.3: RED (#1)1. We have a failure on ovirt-engine-metrics due to a dependency to a new ansible package that has not been synced yet to centos repo.I am adding virt-sig-common repo until this is synced next week:
CQ-Master: RED (#1)1. same failure on ovirt-engine-metrics as 4.3
2. ovirt-hosted-engine-setup is failing due to package dependency change from python-libguestfs to python2-libguestfs. mail sent to Ido to check the issue.Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here:[1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-queue-tester/
[2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-queue-tester/
[3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change-queue-tester/
Happy week!Dafna
-------------------------------------------------------------------------------------------------------------------
COLOUR MAPGreen = job has been passing successfully
** green for more than 3 days may suggest we need a review of our test coverage
1-3 days GREEN (#1)
4-7 days GREEN (#2)
Over 7 days GREEN (#3)
Yellow = intermittent failures for different projects but no lasting or current regressions
** intermittent would be a healthy project as we expect a number of failures during the week
** I will not report any of the solved failures or regressions.
Solved job failures YELLOW (#1)
Solved regressions YELLOW (#2)
Red = job has been failing
** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported.
1-3 days RED (#1)
4-7 days RED (#2)
Over 7 days RED (#3)