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| pw141996-141997 [PATCH] [2/2] net/mlx5: add hairpin out of
Date: Mon, 01 Jul 2024 16:53:28 -0700 (PDT)	[thread overview]
Message-ID: <66834178.170a0220.70e73.097cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240701181245.128810-3-shperetz@nvidia.com>

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

_Testing pending_

Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Monday, July 01 2024 18:12:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0ccf0d5588f7a9d25393351409b4c7497aa8dc74

141996-141997 --> testing pending

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2019 | PASS               | PASS                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS               | PASS                 | PEND              |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.3        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+


Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-01 23:53 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240701181245.128810-3-shperetz@nvidia.com>
2024-07-01 17:46 ` |SUCCESS| pw141996-141997 [PATCH 2/2] net/mlx5: add hairpin out of buffer counter qemudev
2024-07-01 17:51 ` qemudev
2024-07-01 18:14 ` |SUCCESS| pw141997 " checkpatch
2024-07-01 23:11 ` |SUCCESS| pw141996-141997 [PATCH] [2/2] net/mlx5: add hairpin out of dpdklab
2024-07-01 23:13 ` |PENDING| " dpdklab
2024-07-01 23:17 ` dpdklab
2024-07-01 23:17 ` dpdklab
2024-07-01 23:24 ` |SUCCESS| " dpdklab
2024-07-01 23:26 ` dpdklab
2024-07-01 23:30 ` dpdklab
2024-07-01 23:33 ` |PENDING| " dpdklab
2024-07-01 23:35 ` dpdklab
2024-07-01 23:37 ` |SUCCESS| " dpdklab
2024-07-01 23:39 ` |PENDING| " dpdklab
2024-07-01 23:40 ` dpdklab
2024-07-01 23:45 ` |SUCCESS| " dpdklab
2024-07-01 23:48 ` |PENDING| " dpdklab
2024-07-01 23:53 ` dpdklab [this message]
2024-07-01 23:54 ` |SUCCESS| " dpdklab
2024-07-01 23:59 ` dpdklab
2024-07-02  0:12 ` |PENDING| " dpdklab
2024-07-02  0:15 ` |SUCCESS| " dpdklab
2024-07-02  0:20 ` dpdklab
2024-07-02  0:24 ` dpdklab
2024-07-02  0:44 ` dpdklab
2024-07-02  0:45 ` |PENDING| " dpdklab
2024-07-02  1:08 ` dpdklab
2024-07-02  1:32 ` dpdklab
2024-07-02  1:36 ` dpdklab
2024-07-02  1:37 ` dpdklab
2024-07-02  1:44 ` dpdklab
2024-07-02  1:48 ` dpdklab
2024-07-02  1:50 ` dpdklab
2024-07-02  1:54 ` dpdklab
2024-07-02  1:57 ` dpdklab
2024-07-02  2:00 ` dpdklab
2024-07-02  2:01 ` dpdklab
2024-07-02  2:02 ` dpdklab
2024-07-02  2:03 ` dpdklab
2024-07-02  2:03 ` dpdklab
2024-07-02  2:03 ` dpdklab
2024-07-02  2:06 ` dpdklab
2024-07-02  2:07 ` dpdklab
2024-07-02  2:08 ` dpdklab
2024-07-02  2:10 ` dpdklab
2024-07-02  2:15 ` dpdklab
2024-07-02  2:15 ` dpdklab
2024-07-02  2:16 ` dpdklab
2024-07-02  2:16 ` dpdklab
2024-07-02  2:18 ` dpdklab
2024-07-02  2:20 ` |SUCCESS| " dpdklab
2024-07-02  2:23 ` |PENDING| " dpdklab
2024-07-02  2:29 ` dpdklab
2024-07-02  2:34 ` dpdklab
2024-07-02  2:34 ` dpdklab
2024-07-02  2:35 ` dpdklab
2024-07-02  2:37 ` dpdklab
2024-07-02  2:56 ` |SUCCESS| " dpdklab
2024-07-02  4:29 ` |PENDING| " dpdklab
2024-07-02  4:30 ` dpdklab
2024-07-02  4:30 ` dpdklab
2024-07-02  4:30 ` dpdklab
2024-07-02  4:31 ` dpdklab
2024-07-02  4:31 ` dpdklab
2024-07-02  4:34 ` dpdklab
2024-07-02  4:39 ` dpdklab
2024-07-02  4:45 ` dpdklab
2024-07-02  4:45 ` dpdklab
2024-07-02  4:46 ` dpdklab
2024-07-02  4:46 ` dpdklab
2024-07-02  4:47 ` dpdklab
2024-07-02  4:47 ` dpdklab
2024-07-02  4:49 ` dpdklab
2024-07-02  4:49 ` dpdklab
2024-07-02  4:51 ` dpdklab
2024-07-02  4:57 ` dpdklab
2024-07-02  4:57 ` dpdklab
2024-07-02  4:58 ` dpdklab
2024-07-02  5:03 ` dpdklab
2024-07-02  5:04 ` dpdklab
2024-07-02  5:05 ` dpdklab
2024-07-02  5:06 ` dpdklab
2024-07-02  5:06 ` dpdklab
2024-07-02  5:12 ` dpdklab
2024-07-02  5:16 ` dpdklab
2024-07-02  5:17 ` dpdklab
2024-07-02  5:19 ` dpdklab
2024-07-02  5:22 ` dpdklab
2024-07-02  5:24 ` dpdklab
2024-07-02  5:30 ` dpdklab
2024-07-02  5:34 ` |SUCCESS| " dpdklab
2024-07-02  5:40 ` |PENDING| " dpdklab
2024-07-02  5:55 ` dpdklab
2024-07-02  6:11 ` |SUCCESS| " dpdklab
2024-07-02  6:12 ` dpdklab
2024-07-02  6:15 ` |PENDING| " dpdklab
2024-07-02  6:24 ` dpdklab
2024-07-02  6:33 ` dpdklab
2024-07-02  7:00 ` dpdklab
2024-07-02  7:10 ` dpdklab
2024-07-02  7:13 ` dpdklab
2024-07-02  7:20 ` dpdklab
2024-07-02  7:23 ` dpdklab
2024-07-02  7:26 ` dpdklab
2024-07-02  7:30 ` dpdklab
2024-07-02  7:33 ` dpdklab
2024-07-02  7:43 ` dpdklab
2024-07-02  7:48 ` dpdklab
2024-07-02  7:50 ` dpdklab
2024-07-02  7:56 ` dpdklab
2024-07-02  7:58 ` |SUCCESS| " dpdklab
2024-07-02  8:16 ` dpdklab
2024-07-02 15:39 ` dpdklab
2024-07-02 15:48 ` dpdklab
2024-07-02 16:01 ` 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=66834178.170a0220.70e73.097cSMTPIN_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).