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 <ferruh.yigit@intel.com>
>> Sent: Wednesday, October 6, 2021 5:46 AM
>> To: Lincoln Lavoie <lylavoie@iol.unh.edu>; dev <dev@dpdk.org>; Yang, Qiming
>> <qiming.yang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
>> Cc: ci@dpdk.org; Aaron Conole <aconole@redhat.com>; dpdklab
>> <dpdklab@iol.unh.edu>; Singh, Aman Deep <aman.deep.singh@intel.com>;
>> David Marchand <david.marchand@redhat.com>
>> 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
+1-603-674-2755 (m)