DPDK CI discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] [dpdk-dev] DPDK Release Status Meeting 20/05/2021
Date: Thu, 20 May 2021 15:19:09 -0400	[thread overview]
Message-ID: <f7tbl95b4cy.fsf@redhat.com> (raw)
In-Reply-To: <9628dbc9-9fcc-6a1a-d389-75896ad2f392@intel.com> (Ferruh Yigit's message of "Thu, 20 May 2021 13:51:47 +0100")

Ferruh Yigit <ferruh.yigit@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.

> Thanks,
> ferruh


  reply	other threads:[~2021-05-20 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <YKZSyX8NJuMZ4fY5@silpixa00399752>
2021-05-20 12:51 ` Ferruh Yigit
2021-05-20 19:19   ` Aaron Conole [this message]
2021-05-24 12:02     ` Ferruh Yigit
2021-05-24 12:13       ` Ali Alnubani
2021-05-24 16:11         ` Ferruh Yigit
2021-06-17 14:43           ` Lincoln Lavoie
2021-06-17 17:06             ` Ali Alnubani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7tbl95b4cy.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).