Open Stack

On 2022/09/15 17:29, ueha.ayumu at fujitsu.com wrote:
> Hi Yasufumi,
> 
> I think waiting patches don't depend on these tests
> because these tests are for legacy implementation of Tacker.
Thanks for the reply quickly. I've realized that. So, could you update 
your patch for canceling these tests if no other one opposite to the 
temporary fix?

Yasufumi

> 
> -----Original Message-----
> 
> Ayumu,
> 
> On 2022/09/15 17:15, ueha.ayumu at fujitsu.com wrote:
>> Hi Yasufumi,
>>
>> Thanks for your suggestion! I agree with you.
>>
>>> we can make the new tests non-voting
>> I think it is better to make the old tests (legacy and lib-master)
>> non-voting too, because the old tests has also failed recently.
>> What do you think?
> I'd agree if waiting patches don't depend on these tests.
> 
>>
>> Best regards,
>> Ueha
>>
>> -----Original Message-----
>> From: Yasufumi Ogawa <yasufum.o at gmail.com>
>> Sent: Thursday, September 15, 2022 5:00 PM
>> To: openstack-discuss <openstack-discuss at lists.openstack.org>
>> Subject: [tacker] Recent FT errors
>>
>> Hi tacker team,
>>
>> We've several unexpected failures on functional tests since last week or so. It might be because of new tests introduced in the recent some updates, and some lackness of resources on zuul tests we usually meet the same situation at the end of release possibly.
>>
>> Thanks to ueha to propose a patch [1] as a remedy for the issue, but it doesn't work for now unfortunately. For plan B, we can make the new tests non-voting for a while because it's not related to all reamined patches being reviewed now actually. We can revert it and focus on to fix the problem after RC1 is released. What do you think?
>>
>> [1] https://review.opendev.org/c/openstack/tacker/+/857551
>>
>> Yasufumi
>>