From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4CA81A0563 for ; Wed, 15 Apr 2020 19:11:55 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 16E551D95B; Wed, 15 Apr 2020 19:11:55 +0200 (CEST) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) by dpdk.org (Postfix) with ESMTP id 938601D95A for ; Wed, 15 Apr 2020 19:11:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1586970713; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=DrP0bF3UtpDckAIrGGQpDcC34Hnp1qe16WRrdNSAXf4=; b=Dps3Cb3z8Ku07/rbimWFoFojWbTOYY09Qvgzdho9MWz0CRFK7FJwV9hBPNBXZsEGdqaR+7 VRWabwjaoiTPbgsjTkiq9XUMN4RIOzrwViXAG5dSnbJgxV4CLmZ43+ptKdBoGO6GyHIaYF 7QrDczIg4dBDvNkvGpqewiqZV+3yHcQ= 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-238-NkGa0PGHMcmRulhdKPytZA-1; Wed, 15 Apr 2020 13:11:45 -0400 X-MC-Unique: NkGa0PGHMcmRulhdKPytZA-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 7AA9813F8; Wed, 15 Apr 2020 17:11:43 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (ovpn-116-136.phx2.redhat.com [10.3.116.136]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6560D11A267; Wed, 15 Apr 2020 17:11:39 +0000 (UTC) From: Aaron Conole To: Ferruh Yigit Cc: David Marchand , Ajit Khaparde , sys_stv@intel.com, "Chen\, Zhaoyan" , Lincoln Lavoie , "'ci\@dpdk.org'" References: <84e9b2f8-9f5f-63fb-7191-5dfb17489fa1@intel.com> Date: Wed, 15 Apr 2020 13:11:38 -0400 In-Reply-To: <84e9b2f8-9f5f-63fb-7191-5dfb17489fa1@intel.com> (Ferruh Yigit's message of "Wed, 15 Apr 2020 17:45:24 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-ci] Understanding results of patchwork X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 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 4/15/2020 5:42 PM, David Marchand wrote: >> On Wed, Apr 15, 2020 at 6:34 PM Ferruh Yigit wr= ote: >>> >>> On 4/15/2020 3:40 PM, Ajit Khaparde wrote: >>>> Ferruh, >>>> I am trying to apply this patchset. >>>> https://patchwork.dpdk.org/project/dpdk/list/?series=3D9386 >>>> >>>> So I am trying to check if the patches passed all the checks. >>>> I can see only the checkpatch for individual patches and the >>>> travis result - presumably for the complete set. >>>> >>>> https://travis-ci.com/ovsrobot/dpdk/builds/160349438 >>>> >>>> For previous versions, I had seen results for individual patches and p= erformance >>>> results also. Is it enough to apply the patches based on just the trav= is and >>>> checkpatch results? >>>> >>> >>> Hi Ajit, >>> >>> We expect other checks, cc'ed David too. >>=20 >> Better to Cc: ci@dpdk.org from my pov. > > Agree, cc'ed now. > >>=20 >>=20 >>> >>> Intel-compilation seems not sending the reports for a day, last one is = from >>> yesterday, it may be stuck in some set, etc.. @Zhaoyan, can you please = check it? >>> >>> The community lab one is still on pending state, it may be because it i= s a big >>> patchset. >>> https://lab.dpdk.org/results/dashboard/patchsets/10445/ >>> >>> >>> And @David, @Aaron, does travis checks patchset only or does it checks = each >>> patch in set? >>=20 >> Travis checks the whole patchset at the last patch. > > Thanks, so we are missing patch by patch checks in our CI checks, since a= s far > as I know Intel check is also for patchset. For now, we only check the series as a whole in travis to save on time. It's expected that someone / something else would do patch-at-a-time for the series, to preserve the ability to bisect through series. >> The dpdk.org server sends checkpatch reports for each patch. >>=20