DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: Failing kernel module tests and test frequency question
Date: Thu, 6 Jul 2023 13:50:20 -0400	[thread overview]
Message-ID: <CAJvnSUA_Jt9ew9LoEbO+V+ewnCd2nkx91yw1y0OyCWcT_2r9dg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

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/

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

-- 

Patrick Robb

Technical Service Manager

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

www.iol.unh.edu

[-- Attachment #2: Type: text/html, Size: 3030 bytes --]

             reply	other threads:[~2023-07-06 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 17:50 Patrick Robb [this message]
2023-07-06 19:42 ` Ferruh Yigit
2023-07-11 10:12   ` Ferruh Yigit
2023-07-13  8:56     ` Ferruh Yigit
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=CAJvnSUA_Jt9ew9LoEbO+V+ewnCd2nkx91yw1y0OyCWcT_2r9dg@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=ferruh.yigit@amd.com \
    /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).