[ovirt-devel] Re: [Ovirt] [CQ weekly status] [02-08-2019]

2019-08-05 Thread Doron Fediuck 
Yes, but we'd like to make 4.2 d/s only.
Any reasons not to?

On Mon, 5 Aug 2019 at 18:55, Dafna Ron  wrote:

>  I think I saw some projects still merging to 4.2
>
> On Mon, Aug 5, 2019 at 5:44 PM Eyal Edri  wrote:
>
>>
>>
>> On Mon, Aug 5, 2019 at 5:23 PM Dusan Fodor  wrote:
>>
>>>
>>>
>>> On Mon, Aug 5, 2019 at 11:22 AM Sandro Bonazzola 
>>> wrote:
>>>


 Il giorno ven 2 ago 2019 alle ore 22:50 Dusan Fodor 
 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 failuresYELLOW (#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-le...@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 RHV

 Red Hat EMEA 

 sbona...@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 -- in...@ovirt.org
>> To unsubscribe send an email to infra-le...@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/in...@ovirt.org/message/IUUPA6RTP5BMBQC4JYWEYTYKQC6BCN2H/
>>
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement:

[ovirt-devel] Re: [Ovirt] [CQ weekly status] [02-08-2019]

2019-08-05 Thread Dafna Ron 
 I think I saw some projects still merging to 4.2

On Mon, Aug 5, 2019 at 5:44 PM Eyal Edri  wrote:

>
>
> On Mon, Aug 5, 2019 at 5:23 PM Dusan Fodor  wrote:
>
>>
>>
>> On Mon, Aug 5, 2019 at 11:22 AM Sandro Bonazzola 
>> wrote:
>>
>>>
>>>
>>> Il giorno ven 2 ago 2019 alle ore 22:50 Dusan Fodor 
>>> 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 failuresYELLOW (#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-le...@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 RHV
>>>
>>> Red Hat EMEA 
>>>
>>> sbona...@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 -- in...@ovirt.org
> To unsubscribe send an email to infra-le...@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/in...@ovirt.org/message/IUUPA6RTP5BMBQC4JYWEYTYKQC6BCN2H/
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/DPELS26ERWH464APDF3SRFGSMSXOK3QQ/

[ovirt-devel] Re: [Ovirt] [CQ weekly status] [02-08-2019]

2019-08-05 Thread Eyal Edri 
On Mon, Aug 5, 2019 at 5:23 PM Dusan Fodor  wrote:

>
>
> On Mon, Aug 5, 2019 at 11:22 AM Sandro Bonazzola 
> wrote:
>
>>
>>
>> Il giorno ven 2 ago 2019 alle ore 22:50 Dusan Fodor 
>> 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 failuresYELLOW (#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-le...@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 RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@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)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/IUUPA6RTP5BMBQC4JYWEYTYKQC6BCN2H/

[ovirt-devel] Re: [Ovirt] [CQ weekly status] [02-08-2019]

2019-08-05 Thread Dusan Fodor 
On Mon, Aug 5, 2019 at 11:22 AM Sandro Bonazzola 
wrote:

>
>
> Il giorno ven 2 ago 2019 alle ore 22:50 Dusan Fodor 
> 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
>
>
>
>>
>> *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 failuresYELLOW (#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-le...@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 RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> *Red Hat respects your work life balance.
> Therefore there is no need to answer this email out of your office hours.
> *
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/JN6MB7HTC3RDJRYZYYD57USB2HLTNSCE/

[ovirt-devel] Network tests failing randomly again: AssertionError: '192.168.98.1/29' unexpectedly found in ['192.168.99.1/29', '192.168.98.1/29', 'fe80::3c92:48ff:fecd:8366/64']

2019-08-05 Thread Nir Soffer 
This used to happen randomly in the past, and started to happen again.

I can ignore this failure and merge, but this may fail the change queue.

Build:

https://jenkins.ovirt.org/job/vdsm_standard-check-patch/9520//artifact/check-patch.tests-py27.el7.x86_64/mock_logs/script/stdout_stderr.log


==
FAIL: test_add_delete_ipv4 (network.ip_address_test.IPAddressTest)
--
Traceback (most recent call last):
  File 
"/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
line 222, in test_add_delete_ipv4
self._test_add_delete(IPV4_A_WITH_PREFIXLEN, IPV4_B_WITH_PREFIXLEN)
  File 
"/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
line 247, in _test_add_delete
self._assert_has_no_address(nic, ip_b)
  File 
"/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
line 344, in _assert_has_no_address
self._assert_address_not_in(address_with_prefixlen, addresses)
  File 
"/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
line 352, in _assert_address_not_in
self.assertNotIn(address_with_prefixlen, addresses_list)
AssertionError: '192.168.98.1/29' unexpectedly found in
['192.168.99.1/29', '192.168.98.1/29', 'fe80::3c92:48ff:fecd:8366/64']
 >> begin captured logging << 
2019-08-05 12:27:49,718 DEBUG (MainThread) [root] /sbin/ip link add
name dummy_GmE1I type dummy (cwd None) (cmdutils:130)
2019-08-05 12:27:49,731 DEBUG (MainThread) [root] SUCCESS:  = '';
 = 0 (cmdutils:138)
2019-08-05 12:27:49,733 DEBUG (netlink/events) [root] START thread
 (func=>, args=(), kwargs={}) (concurrent:193)
2019-08-05 12:27:49,734 DEBUG (MainThread) [root] /sbin/ip link set
dev dummy_GmE1I up (cwd None) (cmdutils:130)
2019-08-05 12:27:49,746 DEBUG (MainThread) [root] SUCCESS:  = '';
 = 0 (cmdutils:138)
2019-08-05 12:27:49,749 DEBUG (netlink/events) [root] FINISH thread

(concurrent:196)
2019-08-05 12:27:49,755 DEBUG (MainThread) [root] /sbin/ip -4 addr add
dev dummy_GmE1I 192.168.99.1/29 (cwd None) (cmdutils:130)
2019-08-05 12:27:49,763 DEBUG (MainThread) [root] SUCCESS:  = '';
 = 0 (cmdutils:138)
2019-08-05 12:27:49,767 DEBUG (MainThread) [root] /sbin/ip -4 addr add
dev dummy_GmE1I 192.168.98.1/29 (cwd None) (cmdutils:130)
2019-08-05 12:27:49,778 DEBUG (MainThread) [root] SUCCESS:  = '';
 = 0 (cmdutils:138)
2019-08-05 12:27:49,785 DEBUG (MainThread) [root] /sbin/ip -4 addr del
dev dummy_GmE1I 192.168.98.1/29 (cwd None) (cmdutils:130)
2019-08-05 12:27:49,796 DEBUG (MainThread) [root] SUCCESS:  = '';
 = 0 (cmdutils:138)
2019-08-05 12:27:49,803 DEBUG (MainThread) [root] /sbin/ip link del
dev dummy_GmE1I (cwd None) (cmdutils:130)
2019-08-05 12:27:49,824 DEBUG (MainThread) [root] SUCCESS:  = '';
 = 0 (cmdutils:138)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/LF2FAQFGH35FRA25FS3BDQ7PVVLI2G4S/

[ovirt-devel] ovirt-engine has been tagged (ovirt-engine-4.3.5.5)

2019-08-05 Thread Tal Nisan 

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/ULPNJYM4OGVHIZDC6O67VZTX6J2C4HVK/

[ovirt-devel] Re: [Ovirt] [CQ weekly status] [02-08-2019]

2019-08-05 Thread Sandro Bonazzola 
Il giorno ven 2 ago 2019 alle ore 22:50 Dusan Fodor  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



>
> *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


>
> *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 failuresYELLOW (#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-le...@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 RHV

Red Hat EMEA 

sbona...@redhat.com
*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.
*
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/ULQRB2L2AG4OVMGAJ2URH2UXP5GNUN7H/