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: |SUCCESS| pw144147-144148 [PATCH] [v4,2/2] app/testpmd: add set dev
Date: Wed, 18 Sep 2024 00:53:35 -0700 (PDT)	[thread overview]
Message-ID: <66ea86ff.050a0220.224ca7.33a9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240918023847.2964100-3-chaoyong.he@corigine.com>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/144148

_Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Wednesday, September 18 2024 02:38:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:523fd7b3adfdf5a87651e8ca33bc69223b3211d5

144147-144148 --> testing pass

Upstream job id: Windows-Compile-DPDK-Native#22308

Test environment and result as below:

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


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

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-18  7:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240918023847.2964100-3-chaoyong.he@corigine.com>
2024-09-18  2:12 ` |SUCCESS| pw144147-144148 [PATCH v4 2/2] app/testpmd: add set dev led on/off command qemudev
2024-09-18  2:16 ` qemudev
2024-09-18  2:39 ` |SUCCESS| pw144148 " checkpatch
2024-09-18  6:34 ` |SUCCESS| pw144147-144148 [PATCH] [v4,2/2] app/testpmd: add set dev dpdklab
2024-09-18  6:42 ` dpdklab
2024-09-18  7:17 ` dpdklab
2024-09-18  7:42 ` |PENDING| " dpdklab
2024-09-18  7:53 ` dpdklab [this message]
2024-09-18  7:54 ` |SUCCESS| " dpdklab
2024-09-18  7:55 ` dpdklab
2024-09-18  7:55 ` dpdklab
2024-09-18  7:57 ` dpdklab
2024-09-18  8:03 ` |PENDING| " dpdklab
2024-09-18 10:01 ` |SUCCESS| " dpdklab
2024-09-18 11:52 ` dpdklab
2024-09-18 12:28 ` dpdklab
2024-09-18 12:35 ` dpdklab
2024-09-18 13:03 ` dpdklab
2024-09-18 13:07 ` dpdklab
2024-09-19  0: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=66ea86ff.050a0220.224ca7.33a9SMTPIN_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).