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| pw144838-144855 [PATCH] [v3,18/18] net/cnxk: support Tx mu
Date: Tue, 01 Oct 2024 11:28:19 -0700 (PDT)	[thread overview]
Message-ID: <66fc3f43.050a0220.1794ea.8330SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241001124053.3774325-19-ndabilpuram@marvell.com>

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

_Testing pending_

Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Tuesday, October 01 2024 12:40:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ae03728dd31175d055f7df4e141f9944eccf9444

144838-144855 --> testing pending

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

Test environment and result as below:

+---------------------+--------------------+-----------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_win_llvm_compile | dpdk_mingw64_compile |
+=====================+====================+=======================+======================+
| FreeBSD 13.4        | PASS               | SKIPPED               | SKIPPED              |
+---------------------+--------------------+-----------------------+----------------------+
| FreeBSD 14.1        | PEND               | SKIPPED               | SKIPPED              |
+---------------------+--------------------+-----------------------+----------------------+
| Windows Server 2022 | SKIPPED            | PEND                  | PEND                 |
+---------------------+--------------------+-----------------------+----------------------+


FreeBSD 13.4
	Kernel: 13.4-RELEASE-p1
	Compiler: clang 18.1.6

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

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/31207/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-01 18:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241001124053.3774325-19-ndabilpuram@marvell.com>
2024-10-01 12:22 ` |SUCCESS| pw144838-144855 [PATCH v3 18/18] net/cnxk: support Tx multi-seg in vector for cn20k qemudev
2024-10-01 12:27 ` qemudev
2024-10-01 12:44 ` |SUCCESS| pw144855 " checkpatch
2024-10-01 13:45 ` |FAILURE| " 0-day Robot
2024-10-01 18:25 ` |SUCCESS| pw144838-144855 [PATCH] [v3,18/18] net/cnxk: support Tx mu dpdklab
2024-10-01 18:28 ` dpdklab [this message]
2024-10-01 18:32 ` dpdklab
2024-10-01 18:38 ` dpdklab
2024-10-01 18:40 ` dpdklab
2024-10-01 18:40 ` dpdklab
2024-10-01 18:44 ` dpdklab
2024-10-01 18:51 ` dpdklab
2024-10-01 18:56 ` dpdklab
2024-10-01 18:59 ` |PENDING| " dpdklab
2024-10-01 19:43 ` dpdklab
2024-10-01 20:58 ` |SUCCESS| " dpdklab
2024-10-01 22:24 ` dpdklab
2024-10-01 23:04 ` |PENDING| " dpdklab
2024-10-02  0:26 ` |SUCCESS| " dpdklab
2024-10-02  0:32 ` dpdklab
2024-10-02  0:55 ` dpdklab
2024-10-02  1:46 ` dpdklab
2024-10-02  3:50 ` dpdklab
2024-10-02  5:31 ` dpdklab
2024-10-02 10:53 ` 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=66fc3f43.050a0220.1794ea.8330SMTPIN_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).