On Mon, Aug 5, 2019 at 5:23 PM Dusan Fodor <dfodor@redhat.com> wrote:

On Mon, Aug 5, 2019 at 11:22 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Il giorno ven 2 ago 2019 alle ore 22:50 Dusan Fodor <dfodor@redhat.com> ha scritto:

Hi,

This mail is to provide the current status of CQ and allow people to review status before and after the weekend.
Please refer to below colour map for further information on the meaning of the colours.

CQ-4.2:  RED (#1)

Last failure was on 01-08 for ovirt-ansible-hosted-engine-setup caused by missing dependency, patch is pending to fix this.

I think we can close 4.2 CQ, 4.2 gone EOL a few months ago

Can we drop it in upstream? 

In downstream its running 4.2 EUS with 4.3 engine.

 

 

CQ-4.3:   RED (#1)

Last failure was on 02-08 for vdsm caused by missing dependency, patch is pending to fix this.

Have we got a bug for this? If not please open one

It was already resolved by https://gerrit.ovirt.org/#/c/102317/

 

CQ-Master:  RED (#1)

Last failure was on 02-08 for ovirt-engine due failure in build-artifacts, which was caused by gerrit issue, which was reported Evgheni.

     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/

Have a nice week!

Dusan

-------------------------------------------------------------------------------------------------------------------
COLOUR MAP

Green = job has been passing successfully

** green for more than 3 days may suggest we need a review of our test coverage

1. 1-3 days       GREEN (#1)

2. 4-7 days       GREEN (#2)

3. 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.

1. Solved job failures        YELLOW (#1)

2. 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. 1-3 days      RED (#1)

2. 4-7 days      RED (#2)

3. Over 7 days RED (#3)

_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YCNCKRK3G4EJXA3OCYAUS4VMKRDA67F4/

--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

sbonazzo@redhat.com   

Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

--

Eyal edri

He / Him / His

MANAGER

CONTINUOUS PRODUCTIZATION

SYSTEM ENGINEERING

Red Hat

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)

_______________________________________________
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/IUUPA6RTP5BMBQC4JYWEYTYKQC6BCN2H/