[dpdk-ci] [dpdk-dev] DPDK Release Status Meeting 20/05/2021

[Ferruh Yigit]

On 5/20/2021 8:19 PM, Aaron Conole wrote:
> Ferruh Yigit <ferruh.yigit at intel.com> writes:
> 
>> On 5/20/2021 1:15 PM, Ferruh Yigit wrote:
>>> Release status meeting minutes {Date}
>>> =====================================
>>> :Date: 20 May 2021
>>> :toc:
>>
>> <...>
>>
>>> * Coverity is running regularly
>>>   - Can we have out of cycle run for -rc4? Last run was yesterday.
>>>   - We need a way to verify coverity issues before merging it, will carry topic
>>>     to CI mail list an Aaron
>>
>> Hi Aaron,
>>
>> There is a need to verify coverity fixes before merging them. Do you think can
>> we do that? And should I create a Bugzilla ticket for it?
> 
> I think you can create a BZ for it.  Last I remember, coverity does not
> allow so many frequent builds (without paying?), so there is probably a
> non-technical limitation.  Otherwise, we could simply submit all patch
> series to coverity and look at the results.
> 
> As it stands, there is maybe more thought that has to come with this.
> 
> Maybe we can use a tag that indicates which coverity ID it purports to
> fix, and we can then kick off a run.
> 

Yes, we can only run coverity with the patches that has coverity tag.

Do we know the limitation on the run? Even if we can run once a day I think it
can be enough, coverity already not running daily, in the gap days coverity
patches can be verified.
Also we can skip coverity run if the main branch is not updated since last
check, this can gain some runs too.

Created following Bugzilla:
https://bugs.dpdk.org/show_bug.cgi?id=719

btw, Aaron I didn't able to cc your Red Hat email but found following, can you
confirm it is your email address:
aconole at bytheb.org