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 336B6A0C47; Tue, 12 Oct 2021 15:49:17 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 86324410FC; Tue, 12 Oct 2021 15:49:16 +0200 (CEST) Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) by mails.dpdk.org (Postfix) with ESMTP id E16DB40151; Tue, 12 Oct 2021 15:49:14 +0200 (CEST) Received: from pps.filterd (m0098419.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.1.2/8.16.1.2) with SMTP id 19CDfWru009092; Tue, 12 Oct 2021 09:49:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=subject : to : cc : references : from : message-id : date : in-reply-to : content-type : content-transfer-encoding : mime-version; s=pp1; bh=eOYpal2rqoHKeaV1ZmRTK7dnxRWwhxSANpTZMCR2Onc=; b=LHXboG3KPmJX8WE9biZK8YGTNvc/iLMmm81UyTDE0fryyKuHaTZ8/CXXR4Tg1EQdplHr sVHozAHUD7wMkxWpbat9xsVlLBOFvlgW92lkGeUHUx+5vCzq+NacsK8S5kHr5K7dp3kb TiZTJo/TakaypXzf1vuK8nouGte+hmA2vkGucKmJLNtFdsU47eocdEGG8mVcYbW6OSIC fq1x1bJHweGh4ng0vKC+Xi1Xpyo1h/wijIoqz0Obd0k/3KOz5r61Zeibr3aegXOOvBlh KkqNgM2xSWRuqSDlNPUOCrPLSd7WJktUnybHlX0FR3ocLjGjaPl4Isex+71xFynL0QlB 8w== Received: from pps.reinject (localhost [127.0.0.1]) by mx0b-001b2d01.pphosted.com with ESMTP id 3bnbfh05bf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 12 Oct 2021 09:49:13 -0400 Received: from m0098419.ppops.net (m0098419.ppops.net [127.0.0.1]) by pps.reinject (8.16.0.43/8.16.0.43) with SMTP id 19CDnCMO020464; Tue, 12 Oct 2021 09:49:12 -0400 Received: from ppma03dal.us.ibm.com (b.bd.3ea9.ip4.static.sl-reverse.com [169.62.189.11]) by mx0b-001b2d01.pphosted.com with ESMTP id 3bnbfh05b8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 12 Oct 2021 09:49:12 -0400 Received: from pps.filterd (ppma03dal.us.ibm.com [127.0.0.1]) by ppma03dal.us.ibm.com (8.16.1.2/8.16.1.2) with SMTP id 19CDlMC7016850; Tue, 12 Oct 2021 13:49:12 GMT Received: from b03cxnp07028.gho.boulder.ibm.com (b03cxnp07028.gho.boulder.ibm.com [9.17.130.15]) by ppma03dal.us.ibm.com with ESMTP id 3bk2qbg3k1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 12 Oct 2021 13:49:12 +0000 Received: from b03ledav003.gho.boulder.ibm.com (b03ledav003.gho.boulder.ibm.com [9.17.130.234]) by b03cxnp07028.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 19CDnARP24052386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 12 Oct 2021 13:49:10 GMT Received: from b03ledav003.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 87B146A054; Tue, 12 Oct 2021 13:49:10 +0000 (GMT) Received: from b03ledav003.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3272A6A051; Tue, 12 Oct 2021 13:49:09 +0000 (GMT) Received: from [9.65.202.132] (unknown [9.65.202.132]) by b03ledav003.gho.boulder.ibm.com (Postfix) with ESMTP; Tue, 12 Oct 2021 13:49:08 +0000 (GMT) To: Lincoln Lavoie , Ferruh Yigit Cc: Brandon Lo , "Zhang, Qi Z" , dev , "Yang, Qiming" , "ci@dpdk.org" , Aaron Conole , dpdklab , "Singh, Aman Deep" , David Marchand 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> From: Thinh Tran Message-ID: <566cdc1d-3aea-2e31-0fe6-0c831600a829@linux.vnet.ibm.com> Date: Tue, 12 Oct 2021 08:49:08 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 In-Reply-To: Content-Language: en-US X-TM-AS-GCONF: 00 X-Proofpoint-ORIG-GUID: 9UXvBV7Ii5BhZmhVBfCuzIzWRBfXpRxu X-Proofpoint-GUID: MnCnkff-e-zaAvhag-4BP_SBGpyE1NvE Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Proofpoint-UnRewURL: 0 URL was un-rewritten MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.182.1,Aquarius:18.0.790,Hydra:6.0.425,FMLib:17.0.607.475 definitions=2021-10-12_03,2021-10-12_01,2020-04-07_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 suspectscore=0 impostorscore=0 mlxscore=0 adultscore=0 bulkscore=0 priorityscore=1501 clxscore=1015 mlxlogscore=999 spamscore=0 malwarescore=0 phishscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2109230001 definitions=main-2110120079 Subject: Re: [dpdk-dev] [dpdk-ci] RHEL7 failures X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, Thank you all for helping. I will create a new version for my patch. Thanks, Thinh Tran On 10/12/2021 7:39 AM, Lincoln Lavoie wrote: > 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 ZjQcmQRYFpfptBannerStart > This Message Is From an External Sender > This message came from outside your organization. > ZjQcmQRYFpfptBannerEnd > 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 > > >>>> >> 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 >>; > >>>>       >> 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 > > >>>> > > > >>>>       >> .deep.singh@intel.com/ > > > >>>>       >> > >>>>       >> [2] > >>>>       >> > >>>> > 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) >