DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: ci@dpdk.org, Aaron Conole <aconole@redhat.com>,
	 David Marchand <david.marchand@redhat.com>
Subject: Re: 24.11 periodic testing
Date: Tue, 22 Jul 2025 10:27:17 -0400	[thread overview]
Message-ID: <CAJvnSUCx82geNGo28wKHzASTTYQ-p7CzH71KoH51dVz6mF83hg@mail.gmail.com> (raw)
In-Reply-To: <3a496622-8104-4e9b-aa01-187e41773875@redhat.com>

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

Hi Kevin,

Nightly 24.11 testing:

It looks like the nightly testing is running for 24.11:
https://lab.dpdk.org/results/dashboard/periodic_testing/?branch_id=22&page=0&rerun_status=None

But if you are missing emails I should check that. Can you forward to me
the most recent email you received in your filtered folder so I can see the
most recent example?

24.11-staging:

Thanks for the heads up, this should be fixed now. I see our pipeline doing
a new build from 24.11 staging currently.

Windows:

We need to update our pipeline code to find the devx lib:
https://patchwork.dpdk.org/project/dpdk/patch/1752588889-27133-1-git-send-email-andremue@linux.microsoft.com/
which the team is working on now.

Thanks for reaching out.




On Tue, Jul 22, 2025 at 9:57 AM Kevin Traynor <ktraynor@redhat.com> wrote:

> Hi Patrick,
>
> I'm seeing a few issues since looking at UNH 24.11 periodic testing for
> 24.11.3
>
> --
> I can't see emails about nightly testing results since late May. I have
> them filtered to a folder so only look for them when I need to. It could
> be an issue on my side, though my local filters last saw an email on 05/25.
>
> --
> Windows server 2022 VM is failing since some system updates. David
> mentioned that you were already aware about this issue on other branch.
>
> Comparing pass (Jun 10 <) and fail (Jun 16 >) with unchanged 24.11 code.
>
> < Version: 0.57.2
> ---
> > Version: 1.5.2
>
> ......8<......8<......
>
> 140,445d139
> < Library mlx5devx found: YES
>
> ......8<......8<......
>
> > drivers\common\mlx5\windows\meson.build:10:13: ERROR: C shared or
> static library 'mlx5devx' not found
>
> ......8<......8<......
>
> > A full log can be found at
>
> C:\Users\builder\jenkins\workspace\Windows-Compile-DPDK-Native\dpdk\build\meson-logs\meson-log.txt
>
> --
>
> I've pushed to the 24.11-staging but I don't see anything update on
> dashboard (or emails), could you check if it's moving and if not, give
> it it's bi-annual kick :-)
>
> thanks,
> Kevin.
>
>

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

  reply	other threads:[~2025-07-22 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 13:57 Kevin Traynor
2025-07-22 14:27 ` Patrick Robb [this message]
2025-07-22 14:40   ` Kevin Traynor

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=CAJvnSUCx82geNGo28wKHzASTTYQ-p7CzH71KoH51dVz6mF83hg@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=ktraynor@redhat.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).