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 C4B9BA0C47 for ; Tue, 12 Oct 2021 14:39:31 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B58404117E; Tue, 12 Oct 2021 14:39:31 +0200 (CEST) Received: from mail-ed1-f52.google.com (mail-ed1-f52.google.com [209.85.208.52]) by mails.dpdk.org (Postfix) with ESMTP id 6FCD641172 for ; Tue, 12 Oct 2021 14:39:29 +0200 (CEST) Received: by mail-ed1-f52.google.com with SMTP id g10so79807074edj.1 for ; Tue, 12 Oct 2021 05:39:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WJ02TQ5dDGqp1AHaeScIZc45ATWg5iW1GMR3ulohiiw=; b=dQQzpkrwXOsbdJeziUdLvnV3S+mYwOc66UlSKkwMREi7obLxI1Y46TsqVBzYNuONgz clhcXjvkZQ2cQN4/d6ea4ZMYZU0aYOzBSX/QWE+pm9YDT9LvlFMKiYlHMFtEmyjAv/xc HyFKQ6b+rwgMs5i4X/YjUpzBRgw6/up0kHQfE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WJ02TQ5dDGqp1AHaeScIZc45ATWg5iW1GMR3ulohiiw=; b=YLYZVndrAOwQAWAUepercmlgL6R3H3Qs6IBhUfNaIOVTQABof9I6eHSLHUefO3H6pQ kKozcaRkFZzm7S5KymMg7v3KfUrU4aB8Dco3FbTXbfxbtuoM9HiXJBoW8GCInilGXxLA AvaioOVfrIWn10Z/ez1omoqFrXe33VlXB9g4NS6zhIB/FpaYnoyPf/QAO7RqcV26hZgs 6N5QA6cwWB9P0r0FXrDX43N8tU+WnLnTYQjPlBe/QrKvG1tGoziTVC+bI0cloNcXDPuK 8hK1gnYh+StbN9M2hU+3WUp2/gcXs0vXbdtUd2rZ73B0Za3F6LprlV24++6LPnMe7NrN dSKg== X-Gm-Message-State: AOAM532SCGR0jvONBaDTlRn7I5nust9eW7psQrexW8qj91I3aFEeyhYs NmU+vfsgV4lBT0O/JpWPmjKzVXh44Ibbsg5j3OU0Tg== X-Google-Smtp-Source: ABdhPJy4iliPkwkIHcBxNUIdRvSspdyuu7lWH3plYmv+Ao9F3LLccgjLplU3SL66hx538lTFkz6vbZuq2cZb7JrppjU= X-Received: by 2002:a05:6402:350b:: with SMTP id b11mr28491185edd.341.1634042368501; Tue, 12 Oct 2021 05:39:28 -0700 (PDT) MIME-Version: 1.0 References: <7c1ead6b-6e3a-ad0b-ea80-25dd266db87e@intel.com> <496be70d3a6343a8be1306df53d67e23@intel.com> <3966d240-433c-5398-f49b-aecacd1387ef@linux.vnet.ibm.com> <75ef7155-f8d4-4917-4dda-400340e9d1e2@linux.vnet.ibm.com> In-Reply-To: From: Lincoln Lavoie Date: Tue, 12 Oct 2021 08:39:17 -0400 Message-ID: To: Ferruh Yigit Cc: Thinh Tran , Brandon Lo , "Zhang, Qi Z" , dev , "Yang, Qiming" , "ci@dpdk.org" , Aaron Conole , dpdklab , "Singh, Aman Deep" , David Marchand Content-Type: multipart/alternative; boundary="000000000000ec437805ce2722ae" Subject: Re: [dpdk-ci] [dpdk-dev] RHEL7 failures 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" --000000000000ec437805ce2722ae Content-Type: text/plain; charset="UTF-8" Ferruh and Thinh, Yes, that will also work and should trigger the rebuild to the tip of the current git repo / branch. Apologizes for forgetting that behavior is built into the runner. All, That raises the question, for the planned work to allow triggering rebuilds / reruns through patchwork, what is the expected behavior, rerun exactly what was run before, or move to the current pointer (assuming it's moved on) and build/run on top of that? What best aligns with everyone's expectations, so we don't get confusion, etc.? Cheers, Lincoln On Mon, Oct 11, 2021 at 8:58 PM Ferruh Yigit wrote: > On 10/11/2021 11:45 PM, Thinh Tran wrote: > > Hi Brandon, > > > > Does the rebuild have the fix for RHEL 7? Please check. > > > > I just checked the build status, it still hits the same failure on RHEL > 7: > > https://lab.dpdk.org/results/dashboard/patchsets/19066/ > > Your patch still applied on 'dpdk > (086d426406bd3f6fac96a15bbd871c7fe714bc2d)', > which doesn't have the fix. > It seems 'Rebuild' still using the same commit from dpdk. > > Submitting a new version of the patch can be easiest solution to > run CI on correct version. > > > > > [1502/2903] Compiling C object > drivers/net/ice/base/libice_base.a.p/ice_parser_rt.c.o > > FAILED: drivers/net/ice/base/libice_base.a.p/ice_parser_rt.c.o > > ccache cc -Idrivers/net/ice/base/libice_base.a.p -Idrivers/net/ice/base > -I../drivers/net/ice/base -I. -I.. -Iconfig -I../config -Ilib/eal/include > -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include > -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common > -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs > -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -pipe > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O3 -include > rte_config.h -Wextra -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral > -Wformat-security -Wmissing-declarations -Wmissing-prototypes > -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare > -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-missing-field-initializers > -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API > -DALLOW_INTERNAL_API -Wno-unused-value -Wno-unused-but-set-variable > -Wno-unused-variable -Wno-unused-parameter -MD -MQ > > drivers/net/ice/base/libice_base.a.p/ice_parser_rt.c.o -MF > drivers/net/ice/base/libice_base.a.p/ice_parser_rt.c.o.d -o > drivers/net/ice/base/libice_base.a.p/ice_parser_rt.c.o -c > ../drivers/net/ice/base/ice_parser_rt.c > > ../drivers/net/ice/base/ice_parser_rt.c: In function '_hv_bit_sel': > > ../drivers/net/ice/base/ice_parser_rt.c:201:2: error: dereferencing > type-punned pointer will break strict-aliasing rules > [-Werror=strict-aliasing] > > d64 = *(u64 *)&b[0]; > > ^ > > ../drivers/net/ice/base/ice_parser_rt.c: In function '_reg_bit_sel': > > ../drivers/net/ice/base/ice_parser_rt.c:458:2: error: dereferencing > type-punned pointer will break strict-aliasing rules > [-Werror=strict-aliasing] > > d32 = *(u32 *)&v[0]; > > ^ > > cc1: all warnings being treated as errors > > > > Thanks, > > Thinh Tran > > > > On 10/11/2021 12:17 PM, Brandon Lo wrote: > >> Hi Thinh, > >> > >> I have started a rerun of the patch > >> https://patches.dpdk.org/patch/100042 (patchset > >> https://lab.dpdk.org/results/dashboard/patchsets/19066/). > >> You should see the new results reported over email soon. > >> > >> Thanks, > >> Brandon > >> > >> > >> On Mon, Oct 11, 2021 at 12:39 PM Thinh Tran > wrote: > >>> > >>> Hi Linconln, > >>> > >>> I have this patch set 100042 - build/ppc: enable build support for > Power10 > >>> https://patches.dpdk.org/patch/100042 > >>> > >>> Thanks, > >>> Thinh Tran > >>> > >>> > >>> > >>> On 10/11/2021 9:42 AM, Lincoln Lavoie wrote: > >>>> Hi Thinh, The CI won't automatically go back and retest failures > after a > >>>> patch was applied. This is a corner case, where a bad change was > merged > >>>> and affected all patches downstream of that merge. We can retrigger > >>>> specific patches, just ZjQcmQRYFpfptBannerStart > >>>> This Message Is From an External Sender > >>>> This message came from outside your organization. > >>>> ZjQcmQRYFpfptBannerEnd > >>>> Hi Thinh, > >>>> > >>>> The CI won't automatically go back and retest failures after a patch > was > >>>> applied. This is a corner case, where a bad change was merged and > >>>> affected all patches downstream of that merge. We can retrigger > >>>> specific patches, just let us know the patch number or the URI of the > >>>> patch(es). > >>>> > >>>> Cheers, > >>>> Lincoln > >>>> > >>>> On Mon, Oct 11, 2021 at 10:39 AM Thinh Tran < > thinhtr@linux.vnet.ibm.com > >>>> > wrote: > >>>> > >>>> > >>>> Hi, > >>>> I'm wondering how or when the CI would re-pick up the patches > those > >>>> were > >>>> failed due to this issue? > >>>> > >>>> Regards, > >>>> Thinh Tran > >>>> > >>>> On 10/6/2021 10:40 PM, Zhang, Qi Z wrote: > >>>> > Hi Ferruh, David and Aman: > >>>> > > >>>> > Sorry for late response due to PRC holiday. > >>>> > I have just tested the patch and there is no issue be > >>>> detected for functions > >>>> > Thank you so much for the help! > >>>> > > >>>> > Regards > >>>> > Qi > >>>> > > >>>> >> -----Original Message----- > >>>> >> From: Yigit, Ferruh >>>> > > >>>> >> Sent: Wednesday, October 6, 2021 5:46 AM > >>>> >> To: Lincoln Lavoie >>>> >; dev >>>> >; Yang, Qiming > >>>> >> >; > Zhang, > >>>> Qi Z > > >>>> >> Cc: ci@dpdk.org ; Aaron Conole > >>>> >; dpdklab > >>>> >> >; Singh, > Aman > >>>> Deep aman.deep.singh@intel.com>>; > >>>> >> David Marchand >>>> > > >>>> >> Subject: Re: [dpdk-dev] RHEL7 failures > >>>> >> > >>>> >> On 10/5/2021 8:09 PM, Lincoln Lavoie wrote: > >>>> >>> Hello Qiming and Qi, > >>>> >>> > >>>> >>> The CI is picking up failures when building on RHEL7, where > >>>> warnings > >>>> >>> are being treated as errors. This looks like something has > been > >>>> >>> merged into the mainline, as it's failing across all > patches. > >>>> >>> > >>>> >>> Here is the specific failure: > >>>> >>> > >>>> >>> ./drivers/net/ice/base/ice_parser_rt.c: In function > '_hv_bit_sel': > >>>> >>> ../drivers/net/ice/base/ice_parser_rt.c:201:2: error: > dereferencing > >>>> >>> type-punned pointer will break strict-aliasing rules > >>>> >>> [-Werror=strict-aliasing] > >>>> >>> d64 = *(u64 *)&b[0]; > >>>> >>> ^ > >>>> >>> ../drivers/net/ice/base/ice_parser_rt.c: In function > >>>> '_reg_bit_sel': > >>>> >>> ../drivers/net/ice/base/ice_parser_rt.c:458:2: error: > dereferencing > >>>> >>> type-punned pointer will break strict-aliasing rules > >>>> >>> [-Werror=strict-aliasing] > >>>> >>> d32 = *(u32 *)&v[0]; > >>>> >>> ^ > >>>> >>> cc1: all warnings being treated as errors > >>>> >>> > >>>> >>> You can download a full set of logs from here (for a > failing run): > >>>> >>> https://lab.dpdk.org/results/dashboard/patchsets/19162/ > >>>> > >>>> >>> > >>>> >> > >>>> >> Issue was reported by David, Aman sent the fix [1] and it is > >>>> already merged by > >>>> >> David [2], it should be fixed now, can you please double > check? > >>>> >> > >>>> >> [1] > >>>> >> > >>>> > https://patches.dpdk.org/project/dpdk/patch/20211005115754.34117-1-aman > >>>> < > https://patches.dpdk.org/project/dpdk/patch/20211005115754.34117-1-aman> > >>>> >> .deep.singh@intel.com/ > >>>> >> > >>>> >> [2] > >>>> >> > >>>> > https://git.dpdk.org/dpdk/commit/?id=16b809d144dc2df7f31695b5abc64a809 > >>>> < > https://git.dpdk.org/dpdk/commit/?id=16b809d144dc2df7f31695b5abc64a809> > >>>> >> 021b154 > >>>> > >>>> > >>>> > >>>> -- > >>>> *Lincoln Lavoie* > >>>> Principal Engineer, Broadband Technologies > >>>> 21 Madbury Rd., Ste. 100, Durham, NH 03824 > >>>> lylavoie@iol.unh.edu > >>>> https://www.iol.unh.edu > >>>> +1-603-674-2755 (m) > >>>> > >> > >> > >> > > -- *Lincoln Lavoie* Principal Engineer, Broadband Technologies 21 Madbury Rd., Ste. 100, Durham, NH 03824 lylavoie@iol.unh.edu https://www.iol.unh.edu +1-603-674-2755 (m) --000000000000ec437805ce2722ae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Fer= ruh and Thinh,
=
Yes, that = will also work and should trigger the rebuild to the tip of the current git= repo / branch.=C2=A0 Apologizes for forgetting that behavior is built into= the runner.
All,

That raises the question, for = the planned work to allow triggering rebuilds / reruns through patchwork, w= hat is the expected behavior, rerun exactly what was run before, or move to= the current=C2=A0pointer (assuming it's moved on) and build/run on top= of that?=C2=A0 What best aligns with everyone's expectations, so we do= n't get confusion, etc.?

Cheers,
Lincoln

On Mon, Oct 11, 2021 at 8:58 PM Ferruh Yigit = <ferruh.yigit@intel.com>= ; wrote:
On 10/1= 1/2021 11:45 PM, Thinh Tran wrote:
> Hi Brandon,
>
> Does the rebuild have the fix for RHEL 7? Please check.
>
> I just checked the build status, it still hits the same failure on RHE= L 7:

https://lab.dpdk.org/results/dashboard/patchs= ets/19066/

Your patch still applied on 'dpdk (086d426406bd3f6fac96a15bbd871c7fe714= bc2d)',
which doesn't have the fix.
It seems 'Rebuild' still using the same commit from dpdk.

Submitting a new version of the patch can be easiest solution to
run CI on correct version.

>
> [1502/2903] Compiling C object drivers/net/ice/base/libice_base.a.p/ic= e_parser_rt.c.o
> FAILED: drivers/net/ice/base/libice_base.a.p/ice_parser_rt.c.o
> ccache cc -Idrivers/net/ice/base/libice_base.a.p -Idrivers/net/ice/bas= e -I../drivers/net/ice/base -I. -I.. -Iconfig -I../config -Ilib/eal/include= -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -I= lib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/= common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/metrics -I= ../lib/metrics -Ilib/telemetry -I../lib/telemetry -pipe -D_FILE_OFFSET_BITS= =3D64 -Wall -Winvalid-pch -Werror -O3 -include rte_config.h -Wextra -Wcast-= qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-= declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -= Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -= Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=3Dnative -DALLOW_= EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-unused-value -Wno-unused-but-set= -variable -Wno-unused-variable -Wno-unused-parameter -MD -MQ
> drivers/net/ice/base/libice_base.a.p/ice_parser_rt.c.o -MF drivers/net= /ice/base/libice_base.a.p/ice_parser_rt.c.o.d -o drivers/net/ice/base/libic= e_base.a.p/ice_parser_rt.c.o -c ../drivers/net/ice/base/ice_parser_rt.c
> ../drivers/net/ice/base/ice_parser_rt.c: In function '_hv_bit_sel&= #39;:
> ../drivers/net/ice/base/ice_parser_rt.c:201:2: error: dereferencing ty= pe-punned pointer will break strict-aliasing rules [-Werror=3Dstrict-aliasi= ng]
>=C2=A0 =C2=A0 d64 =3D *(u64 *)&b[0];
>=C2=A0 =C2=A0 ^
> ../drivers/net/ice/base/ice_parser_rt.c: In function '_reg_bit_sel= ':
> ../drivers/net/ice/base/ice_parser_rt.c:458:2: error: dereferencing ty= pe-punned pointer will break strict-aliasing rules [-Werror=3Dstrict-aliasi= ng]
>=C2=A0 =C2=A0 d32 =3D *(u32 *)&v[0];
>=C2=A0 =C2=A0 ^
> cc1: all warnings being treated as errors
>
> Thanks,
> Thinh Tran
>
> On 10/11/2021 12:17 PM, Brandon Lo wrote:
>> Hi Thinh,
>>
>> I have started a rerun of the patch
>> https://patches.dpdk.org/patch/100042 (patchset >> https://lab.dpdk.org/results/dashboa= rd/patchsets/19066/).
>> You should see the new results reported over email soon.
>>
>> Thanks,
>> Brandon
>>
>>
>> On Mon, Oct 11, 2021 at 12:39 PM Thinh Tran <thinhtr@linux.vnet.ibm.com> wrote:
>>>
>>> Hi Linconln,
>>>
>>> I have this patch set 100042=C2=A0 - build/ppc: enable build s= upport for Power10
>>> https://patches.dpdk.org/patch/100042
>>>
>>> Thanks,
>>> Thinh Tran
>>>
>>>
>>>
>>> On 10/11/2021 9:42 AM, Lincoln Lavoie wrote:
>>>> Hi Thinh, The CI won't automatically go back and retes= t failures after a
>>>> patch was applied.=C2=A0 This is a corner case, where a ba= d change was merged
>>>> and affected all patches downstream of that merge.=C2=A0 W= e can retrigger
>>>> specific patches, just ZjQcmQRYFpfptBannerStart
>>>> This Message Is From an External Sender
>>>> This message came from outside your organization.
>>>> ZjQcmQRYFpfptBannerEnd
>>>> Hi Thinh,
>>>>
>>>> The CI won't automatically go back and retest failures= after a patch was
>>>> applied.=C2=A0 This is a corner case, where a bad change w= as merged and
>>>> affected all patches downstream of that merge.=C2=A0 We ca= n retrigger
>>>> specific patches, just let us know the patch number or the= URI of the
>>>> patch(es).
>>>>
>>>> Cheers,
>>>> Lincoln
>>>>
>>>> On Mon, Oct 11, 2021 at 10:39 AM Thinh Tran <thinhtr@linux.vnet.ib= m.com
>>>> <mailto:thinhtr@linux.vnet.ibm.com>> wrote:
>>>>
>>>>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 Hi,
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 I'm wondering how or when the= CI would re-pick up the patches those
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 were
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 failed due to this issue?
>>>>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 Regards,
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 Thinh Tran
>>>>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 On 10/6/2021 10:40 PM, Zhang, Qi = Z wrote:
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 > Hi Ferruh, David and A= man:
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 Sorry for late response due to PRC holiday.
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 I have just tested the patch and there is no issue be
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 detected for functions
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 Thank you so much for the help!
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 > Regards
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 > Qi
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> -----Original Mess= age-----
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> From: Yigit, Ferru= h <ferruh.yi= git@intel.com
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 <mailto:ferruh.yigit@intel.com>> >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> Sent: Wednesday, O= ctober 6, 2021 5:46 AM
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> To: Lincoln Lavoie= <lylavoie@iol= .unh.edu
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 <mailto:lylavoie@iol.unh.edu>>; dev &= lt;dev@dpdk.org
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 <mailto:dev@dpdk.org>>; Yang, Qiming
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> <qiming.yang@intel.com <= mailto:qiming.ya= ng@intel.com>>; Zhang,
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 Qi Z <qi.z.zhang@intel.com <mailto:qi.z.zhang@intel.com>>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> Cc: ci@dpdk.org <mailto:ci@dpdk.org>; Aaron Conole
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 <aconole@redhat.com <mailto:aconole@redhat.com>>; d= pdklab
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> <dpdklab@iol.unh.edu <mail= to:dpdklab@iol.unh= .edu>>; Singh, Aman
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 Deep <aman.deep.singh@intel.com <ma= ilto:aman.de= ep.singh@intel.com>>;
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> David Marchand <= ;david.march= and@redhat.com
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 <mailto:david.marchand@redhat.com>&= gt;
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> Subject: Re: [dpdk= -dev] RHEL7 failures
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> On 10/5/2021 8:09 = PM, Lincoln Lavoie wrote:
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> Hello Qiming a= nd Qi,
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> The CI is pick= ing up failures when building on RHEL7, where
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 warnings
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> are being trea= ted as errors.=C2=A0 This looks like something has been
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> merged into th= e mainline, as it's failing across all patches.
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> Here is the sp= ecific failure:
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> ./drivers/net/= ice/base/ice_parser_rt.c: In function '_hv_bit_sel':
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> ../drivers/net= /ice/base/ice_parser_rt.c:201:2: error: dereferencing
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> type-punned po= inter will break strict-aliasing rules
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> [-Werror=3Dstr= ict-aliasing]
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2= =A0=C2=A0 d64 =3D *(u64 *)&b[0];
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2= =A0=C2=A0 ^
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> ../drivers/net= /ice/base/ice_parser_rt.c: In function
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 '_reg_bit_sel':
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> ../drivers/net= /ice/base/ice_parser_rt.c:458:2: error: dereferencing
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> type-punned po= inter will break strict-aliasing rules
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> [-Werror=3Dstr= ict-aliasing]
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2= =A0=C2=A0 d32 =3D *(u32 *)&v[0];
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2= =A0=C2=A0 ^
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> cc1: all warni= ngs being treated as errors
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> You can downlo= ad a full set of logs from here (for a failing run):
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>> https://lab.dpdk.org/results/dashboard/patchsets/19162/=
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 <https://lab.dpdk.org/results/dashboard/patchsets/19162/>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> Issue was reported= by David, Aman sent the fix [1] and it is
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 already merged by
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> David [2], it shou= ld be fixed now, can you please double check?
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> [1]
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 https://patches.dpdk.org/project/dpdk/patch/20211005115754.341= 17-1-aman
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 <https://patches.dpdk.org/project/dpdk/patch/20211005115754= .34117-1-aman>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> .deep.singh@int= el.com/ <http://deep.singh@intel.com/>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> [2]
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 https://git.dpdk.org/dpdk/commit/?id=3D16b809d144dc2df7f31695= b5abc64a809
>>>> =C2=A0=C2=A0=C2=A0=C2=A0 <https://git.dpdk.org/dpdk/commit/?id=3D16b809d144dc2df7f3= 1695b5abc64a809>
>>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >> 021b154
>>>>
>>>>
>>>>
>>>> --
>>>> *Lincoln Lavoie*
>>>> Principal Engineer, Broadband Technologies
>>>> 21 Madbury Rd., Ste. 100, Durham, NH 03824
>>>> = lylavoie@iol.unh.edu <mailto:lylavoie@iol.unh.edu>
>>>> https://www.iol.unh.edu <https://www.iol.unh.edu>= ;
>>>> +1-603-674-2755 (m)
>>>> <https://www.iol.unh.edu>
>>
>>
>>



--
Lincoln Lavoie
Prin= cipal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, = Durham, NH 03824
+1-603-674-= 2755 (m)

--000000000000ec437805ce2722ae--