DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: ci@dpdk.org, Aaron Conole <aconole@redhat.com>
Subject: Windows compile and unit test jobs
Date: Thu, 23 Jan 2025 14:46:31 -0500	[thread overview]
Message-ID: <CAJvnSUAyuUO+1xOxKTuECbHnrRPKvFVSzkzN3nTUM5umtPwm0Q@mail.gmail.com> (raw)

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

Hello Andre,

Thank you for joining the CI call this morning and for raising the topic of
Windows compile and unit tests at the UNH lab.

I have confirmed we are publishing build results for the 3 compile
toolchain options described on dpdk.org these are:

llvm-clang native compile
mingw64 native compile
msvc native compile

Here is an example of a compile report including these.
https://mails.dpdk.org/archives/test-report/2025-January/845150.html

Some notes about the compile options:

-I have now renamed the clang test from dpdk_win_llvm_compile to
dpdk_llvm_clang_compile to more clearly indicate this is the clang compile,
per our conversation)

-All 3 compile options are also compiling with mlx5 devx using
cflags/ldflags per https://bugs.dpdk.org/show_bug.cgi?id=1174. This request
came in from NVIDIA guys, and we ran it by Tyler from Microsoft who
indicated it was a good idea.

-MSVC does not run unit tests (I believe this is because msvc does not
currently compile enough of dpdk for unit tests)

Is there a particular compile option or set of compile options which you
want to run unit tests after the build? Please let me know anything you
want changed/added to our CI testing pipelines.

Thanks!

-DPDK Community Lab Team

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

                 reply	other threads:[~2025-01-23 19:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAJvnSUAyuUO+1xOxKTuECbHnrRPKvFVSzkzN3nTUM5umtPwm0Q@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=andremue@linux.microsoft.com \
    --cc=ci@dpdk.org \
    /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).