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 313D4A0563 for ; Wed, 15 Apr 2020 19:24:54 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2902F1D965; Wed, 15 Apr 2020 19:24:54 +0200 (CEST) Received: from mail-ot1-f49.google.com (mail-ot1-f49.google.com [209.85.210.49]) by dpdk.org (Postfix) with ESMTP id 609281D961 for ; Wed, 15 Apr 2020 19:24:53 +0200 (CEST) Received: by mail-ot1-f49.google.com with SMTP id m18so652274otq.9 for ; Wed, 15 Apr 2020 10:24:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LoRj+4Kq7vJ6GPtbwDLOSAQhnWBDRgczlESmJhE6Ukg=; b=aayiyTvsR21DoWVXg4KhJQm8z3Ca8EdL8WjjBCy70PqjPrv86zY1ZWzyIZhywCcs+M 11pn9duEgGzdeD4rmMb+E0HfZ6PwyA5p4DsR67wFcuA5s+YaRSaDIiW47u87b0JsA5wv 9E406FfFR8KsCNBCDmsY6IzRE8HrRGMn5+hO8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LoRj+4Kq7vJ6GPtbwDLOSAQhnWBDRgczlESmJhE6Ukg=; b=Pm1erYXcOvBSG/NsUT/H8t4/Reyj21cPS7tSUTR6XwGXyR1uFXOamkPVa1GowpDwyT A59gCRRBag1zVbH/IMur1DKRUTjNyUhB7P1UngFnXcGK/cy2Pah6woY79xzIsKvq5fLV bzahp0FYSdS1cw90TVuuRB3VjuVz2Y67OyO2cF7F76TTuLKtQzt2LLVce7HePP1xOKyI aHyg5eeqteU5p0AnRnWYhvGXsoCprLcFezo4Yh+OY5wz+zrtO2B35fq8cQYGsYNNg9QX ZERXQHo0GvTYjQW0Ys0UYTE2rCmnKDSBqj+MJQNqz03DRLRTNpt1YE2rQQt5i/maigEN b0pw== X-Gm-Message-State: AGi0PubcFO7b4pomUCz23Wq/H0NY3L8z0ZL2PsaijIrLnOHE5sHGjOFQ SRh7weWUauETaiessn4n0cU/bfS5taB1t3PLk9qyLw== X-Google-Smtp-Source: APiQypJy6g7JDAlPbMUmfCdB9yGxeQ3r9SmSn56morRqA2nQobtl6rrURMYfzI2CyGYQw8IwPq8QedY+SzTYmAQDSTQ= X-Received: by 2002:a9d:de2:: with SMTP id 89mr3445653ots.95.1586971492401; Wed, 15 Apr 2020 10:24:52 -0700 (PDT) MIME-Version: 1.0 References: <84e9b2f8-9f5f-63fb-7191-5dfb17489fa1@intel.com> In-Reply-To: From: Ajit Khaparde Date: Wed, 15 Apr 2020 10:24:36 -0700 Message-ID: To: Aaron Conole Cc: Ferruh Yigit , David Marchand , sys_stv@intel.com, "Chen, Zhaoyan" , Lincoln Lavoie , "ci@dpdk.org" Content-Type: multipart/alternative; boundary="00000000000012fb9705a35798be" 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" --00000000000012fb9705a35798be Content-Type: text/plain; charset="UTF-8" On Wed, Apr 15, 2020 at 10:11 AM Aaron Conole wrote: > Ferruh Yigit writes: > > > On 4/15/2020 5:42 PM, David Marchand wrote: > >> On Wed, Apr 15, 2020 at 6:34 PM Ferruh Yigit > wrote: > >>> > >>> 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=9386 > >>>> > >>>> 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 > performance > >>>> results also. Is it enough to apply the patches based on just the > travis and > >>>> checkpatch results? > >>>> > >>> > >>> Hi Ajit, > >>> > >>> We expect other checks, cc'ed David too. > >> > >> Better to Cc: ci@dpdk.org from my pov. > > > > Agree, cc'ed now. > > > >> > >> > >>> > >>> 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 > is 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? > >> > >> Travis checks the whole patchset at the last patch. > > > > Thanks, so we are missing patch by patch checks in our CI checks, since > as 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. > Ok, thanks for the clarification. We went through the exercise. Since this was a big patchset, I was trying to be extra careful. So I wanted to make sure reports for all automated checks are in. That's when I started digging into the reports and the process. Thanks > >> The dpdk.org server sends checkpatch reports for each patch. > >> > > --00000000000012fb9705a35798be Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Apr 15, 2020 at 10:11 AM Aaro= n Conole <aconole@redhat.com&g= t; wrote:
Ferruh= Yigit <ferr= uh.yigit@intel.com> writes:

> On 4/15/2020 5:42 PM, David Marchand wrote:
>> On Wed, Apr 15, 2020 at 6:34 PM Ferruh Yigit <ferruh.yigit@intel.com> w= rote:
>>>
>>> On 4/15/2020 3:40 PM, Ajit Khaparde wrote:
>>>> Ferruh,
>>>> I am trying to apply this patchset.
>>>> https://patchwork.dpdk.o= rg/project/dpdk/list/?series=3D9386
>>>>
>>>> So I am trying to check if the patches passed all the chec= ks.
>>>> I can see only the checkpatch for individual patches and t= he
>>>> travis result - presumably for the complete set.
>>>>
>>>> https://travis-ci.com/ovsrobot/= dpdk/builds/160349438
>>>>
>>>> For previous versions, I had seen results for individual p= atches and performance
>>>> results also. Is it enough to apply the patches based on j= ust the travis and
>>>> checkpatch results?
>>>>
>>>
>>> Hi Ajit,
>>>
>>> We expect other checks, cc'ed David too.
>>
>> Better to Cc: ci@= dpdk.org from my pov.
>
> Agree, cc'ed now.
>
>>
>>
>>>
>>> Intel-compilation seems not sending the reports for a day, las= t one is from
>>> yesterday, it may be stuck in some set, etc.. @Zhaoyan, can yo= u please check it?
>>>
>>> The community lab one is still on pending state, it may be bec= ause it is a big
>>> patchset.
>>> https://lab.dpdk.org/results/das= hboard/patchsets/10445/
>>>
>>>
>>> And @David, @Aaron, does travis checks patchset only or does i= t checks each
>>> patch in set?
>>
>> Travis checks the whole patchset at the last patch.
>
> Thanks, so we are missing patch by patch checks in our CI checks, sinc= e as 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.=C2=A0 It's expected that someone / something else would do
patch-at-a-time for the series, to preserve the ability to bisect
through series.
Ok, thanks for the clarification.=C2= =A0
We went through the exercise. Since this was a big patchset,
I was trying= to be extra careful. So I wanted to make sure reports for all
automated che= cks are in. That's when I started digging into the reports
and the proce= ss.

Thanks


>> The dpdk.org server sends checkpatch reports for each patch.
>>

--00000000000012fb9705a35798be--