From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
ci@dpdk.org
Subject: Re: Failing kernel module tests and test frequency question
Date: Thu, 13 Jul 2023 09:56:42 +0100 [thread overview]
Message-ID: <722271b4-169d-f828-dd84-39af6ae377aa@amd.com> (raw)
In-Reply-To: <b8077520-7a0a-26d9-8986-7d976b6f4f3e@amd.com>
On 7/11/2023 11:12 AM, Ferruh Yigit wrote:
> On 7/6/2023 8:42 PM, Ferruh Yigit wrote:
>> On 7/6/2023 6:50 PM, Patrick Robb wrote:
>>> Hello,
>>>
>>> I am seeing our kmods testcase fail on the daily periodic run since June
>>> 29: https://dpdkdashboard.iol.unh.edu/results/dashboard/tarballs/25226/
>>> <https://dpdkdashboard.iol.unh.edu/results/dashboard/tarballs/25226/>
>>>
>>> It does coincide with a slew of patches being merged for rc2. But, I
>>> haven't looked at those patches individually, and I also don't know
>>> whether we generally expect breakages for this kernel module compile job
>>> to come from dpdk patches or from patches on the linux kernel project.
>>>
>>> I understand that the original/current plan was for running the kernel
>>> module test 1x/day. The question this raises for me is, if we were able
>>> to afford expending the needed compute resources for kmod compile
>>> testing on all incoming patchseries, would that be a valuable addition,
>>> or not?
>>>
>>> Thanks,
>>> Patrick
>>>
>>
>> Hi Patrick,
>>
>> It is KNI build failure with latest kernel because of an kernel API
>> change, I am aware of it an have a local patch to fix.
>>
>> But fix requires kernel version check (to detect correct API) and since
>> kernel is in the 6.5 merge window and -rc1 is not out, current version
>> is still 6.4 and version control is not working as expected.
>> In my local patch I am using 6.4 for version check but that is wrong and
>> not suitable for an upstream patch.
>>
>> That is why can you pause the 'dpdk_kmod_compile_torvalds_linux' test
>> until v6.5-rc1 is out, it shouldn't take long.
>>
>
> I have sent following patch, can you please test:
> https://patches.dpdk.org/project/dpdk/patch/20230711100941.2082191-1-ferruh.yigit@amd.com/
>
> You can enable test and use patch locally until it is merged to main repo.
>
Fix merged for -rc3, so test should be OK now.
next prev parent reply other threads:[~2023-07-13 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 17:50 Patrick Robb
2023-07-06 19:42 ` Ferruh Yigit
2023-07-11 10:12 ` Ferruh Yigit
2023-07-13 8:56 ` Ferruh Yigit [this message]
2023-07-13 15:30 ` Patrick Robb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=722271b4-169d-f828-dd84-39af6ae377aa@amd.com \
--to=ferruh.yigit@amd.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).