From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B759CA0A02 for ; Thu, 20 May 2021 21:19:14 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8750340143; Thu, 20 May 2021 21:19:14 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 76F0B40041 for ; Thu, 20 May 2021 21:19:13 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1621538353; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0ja44dvWny+eRxKWu1kZqmY21DOZM0phv18JpBP5xd8=; b=diSmlit4uHRqCnPUOLBN5dagJA8GVSdJpeY2W0ZpgwC4Ln5/HA8zS7zcnmegrwqWomUWWe zoGFJh2kFxUGOKslat1vGVosuePT5qmVNQbAr0YuGpVx8liJVVmXoOgO0KpXaIBKk8lEG3 Gkw7m2/rLsUkgtbGRCghxqj2x0qt8/o= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-32-F9KCWc3TPaiKzNNhFvlGbg-1; Thu, 20 May 2021 15:19:11 -0400 X-MC-Unique: F9KCWc3TPaiKzNNhFvlGbg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9415B802690; Thu, 20 May 2021 19:19:10 +0000 (UTC) Received: from RHTPC1VM0NT (ovpn-118-71.rdu2.redhat.com [10.10.118.71]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3AC2960C4A; Thu, 20 May 2021 19:19:10 +0000 (UTC) From: Aaron Conole To: Ferruh Yigit Cc: "ci@dpdk.org" References: <9628dbc9-9fcc-6a1a-d389-75896ad2f392@intel.com> Date: Thu, 20 May 2021 15:19:09 -0400 In-Reply-To: <9628dbc9-9fcc-6a1a-d389-75896ad2f392@intel.com> (Ferruh Yigit's message of "Thu, 20 May 2021 13:51:47 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=aconole@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: Re: [dpdk-ci] [dpdk-dev] DPDK Release Status Meeting 20/05/2021 X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" Ferruh Yigit 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