automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw154528-154532 [PATCH] [5/5] net/mlx5: support non-templa
Date: Tue, 17 Jun 2025 07:55:01 -0700 (PDT)	[thread overview]
Message-ID: <685181c5.050a0220.22f2d4.69a2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250617133933.313443-5-getelson@nvidia.com>

Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/154532

_Testing pending_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, June 17 2025 13:39:33 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:77ba8d12251b203a4ec69a569c2f2f07edb7b1e8

154528-154532 --> testing pending

Upstream job id: Generic-VM-DPDK-Compile-Meson#36475

Test environment and result as below:

+---------------------+--------------------+-------------------+-------------------------+
|     Environment     | dpdk_meson_compile | dpdk_msvc_compile | dpdk_llvm_clang_compile |
+=====================+====================+===================+=========================+
| FreeBSD 14.2        | PASS               | SKIPPED           | SKIPPED                 |
+---------------------+--------------------+-------------------+-------------------------+
| Windows Server 2022 | SKIPPED            | PEND              | PEND                    |
+---------------------+--------------------+-------------------+-------------------------+


FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33438/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-06-17 14:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250617133933.313443-5-getelson@nvidia.com>
2025-06-17 13:09 ` |SUCCESS| pw154528-154532 [PATCH 5/5] net/mlx5: support non-template SAMPLE flow action qemudev
2025-06-17 13:13 ` qemudev
2025-06-17 13:40 ` |WARNING| pw154532 " checkpatch
2025-06-17 14:46 ` |SUCCESS| " 0-day Robot
2025-06-17 14:51 ` |SUCCESS| pw154528-154532 [PATCH] [5/5] net/mlx5: support non-templa dpdklab
2025-06-17 14:53 ` dpdklab
2025-06-17 14:55 ` dpdklab [this message]
2025-06-17 15:07 ` |FAILURE| " dpdklab
2025-06-17 15:08 ` dpdklab
2025-06-17 15:09 ` |SUCCESS| " dpdklab
2025-06-17 15:10 ` |FAILURE| " dpdklab
2025-06-17 15:12 ` |PENDING| " dpdklab
2025-06-17 15:19 ` dpdklab
2025-06-17 15:27 ` dpdklab
2025-06-17 15:54 ` |SUCCESS| " dpdklab
2025-06-17 15:56 ` dpdklab
2025-06-17 15:56 ` dpdklab
2025-06-17 16:04 ` dpdklab
2025-06-17 16:15 ` dpdklab
2025-06-17 16:24 ` dpdklab
2025-06-17 20:20 ` |PENDING| " dpdklab
2025-06-17 21:30 ` |FAILURE| " dpdklab
2025-06-17 21:36 ` |SUCCESS| " dpdklab
2025-06-17 22:33 ` dpdklab

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=685181c5.050a0220.22f2d4.69a2SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@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).