From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143595 [PATCH] doc: update TAP device features
Date: Wed, 04 Sep 2024 12:35:49 -0700 (PDT) [thread overview]
Message-ID: <66d8b695.d40a0220.373053.0d15SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240904154206.13438-1-stephen@networkplumber.org>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/143595
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, September 04 2024 15:42:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5cce3d463a99dbb5e7797faaed6c68df6c2b549a
143595 --> testing pass
Upstream job id: Windows-Compile-DPDK-Native#21899
Test environment and result as below:
+---------------------+--------------------+-----------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_win_llvm_compile | dpdk_mingw64_compile |
+=====================+====================+=======================+======================+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| FreeBSD 14.1 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+----------------------+
| Windows Server 2022 | SKIPPED | PASS | PASS |
+---------------------+--------------------+-----------------------+----------------------+
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
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/30905/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-09-04 19:35 UTC|newest]
Thread overview: 143+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240904154206.13438-1-stephen@networkplumber.org>
2024-09-04 15:19 ` qemudev
2024-09-04 15:23 ` qemudev
2024-09-04 15:42 ` checkpatch
2024-09-04 16:44 ` 0-day Robot
2024-09-04 19:34 ` dpdklab
2024-09-04 19:35 ` dpdklab [this message]
2024-09-04 19:36 ` dpdklab
2024-09-04 19:36 ` dpdklab
2024-09-04 19:46 ` dpdklab
2024-09-04 19:46 ` dpdklab
2024-09-04 19:47 ` |PENDING| " dpdklab
2024-09-04 19:47 ` dpdklab
2024-09-04 19:51 ` |SUCCESS| " dpdklab
2024-09-04 19:56 ` dpdklab
2024-09-04 19:56 ` dpdklab
2024-09-04 20:00 ` dpdklab
2024-09-04 20:00 ` dpdklab
2024-09-04 20:01 ` dpdklab
2024-09-04 20:08 ` |PENDING| " dpdklab
2024-09-04 20:12 ` dpdklab
2024-09-04 20:13 ` |SUCCESS| " dpdklab
2024-09-04 20:20 ` dpdklab
2024-09-04 20:30 ` dpdklab
2024-09-04 21:07 ` |PENDING| " dpdklab
2024-09-04 22:55 ` |SUCCESS| " dpdklab
2024-09-04 22:56 ` dpdklab
2024-09-04 23:00 ` dpdklab
2024-09-04 23:23 ` dpdklab
2024-09-04 23:24 ` dpdklab
2024-09-04 23:26 ` dpdklab
2024-09-04 23:27 ` dpdklab
2024-09-04 23:28 ` dpdklab
2024-09-04 23:29 ` dpdklab
2024-09-04 23:30 ` dpdklab
2024-09-04 23:30 ` dpdklab
2024-09-04 23:31 ` dpdklab
2024-09-04 23:31 ` dpdklab
2024-09-04 23:32 ` dpdklab
2024-09-04 23:32 ` dpdklab
2024-09-04 23:33 ` dpdklab
2024-09-04 23:34 ` dpdklab
2024-09-04 23:34 ` dpdklab
2024-09-04 23:35 ` dpdklab
2024-09-04 23:36 ` dpdklab
2024-09-04 23:36 ` dpdklab
2024-09-04 23:36 ` dpdklab
2024-09-04 23:37 ` dpdklab
2024-09-04 23:38 ` dpdklab
2024-09-04 23:39 ` dpdklab
2024-09-04 23:39 ` dpdklab
2024-09-04 23:43 ` dpdklab
2024-09-04 23:44 ` dpdklab
2024-09-04 23:45 ` dpdklab
2024-09-04 23:45 ` dpdklab
2024-09-04 23:46 ` dpdklab
2024-09-04 23:46 ` dpdklab
2024-09-04 23:47 ` dpdklab
2024-09-04 23:49 ` dpdklab
2024-09-04 23:49 ` dpdklab
2024-09-05 0:19 ` dpdklab
2024-09-05 0:20 ` dpdklab
2024-09-05 0:21 ` dpdklab
2024-09-05 0:21 ` dpdklab
2024-09-05 0:23 ` dpdklab
2024-09-05 0:23 ` dpdklab
2024-09-05 0:23 ` dpdklab
2024-09-05 0:24 ` dpdklab
2024-09-05 0:24 ` dpdklab
2024-09-05 0:25 ` dpdklab
2024-09-05 0:26 ` dpdklab
2024-09-05 0:26 ` dpdklab
2024-09-05 0:27 ` dpdklab
2024-09-05 0:29 ` dpdklab
2024-09-05 0:30 ` dpdklab
2024-09-05 0:30 ` dpdklab
2024-09-05 0:31 ` dpdklab
2024-09-05 0:33 ` dpdklab
2024-09-05 0:33 ` dpdklab
2024-09-05 0:34 ` dpdklab
2024-09-05 0:34 ` dpdklab
2024-09-05 0:34 ` dpdklab
2024-09-05 0:36 ` dpdklab
2024-09-05 0:36 ` dpdklab
2024-09-05 0:36 ` dpdklab
2024-09-05 0:36 ` dpdklab
2024-09-05 0:38 ` dpdklab
2024-09-05 0:38 ` dpdklab
2024-09-05 0:39 ` dpdklab
2024-09-05 0:42 ` dpdklab
2024-09-05 0:42 ` dpdklab
2024-09-05 0:42 ` dpdklab
2024-09-05 0:43 ` dpdklab
2024-09-05 0:43 ` dpdklab
2024-09-05 0:43 ` dpdklab
2024-09-05 0:44 ` dpdklab
2024-09-05 0:44 ` dpdklab
2024-09-05 0:44 ` dpdklab
2024-09-05 0:45 ` dpdklab
2024-09-05 0:45 ` dpdklab
2024-09-05 0:46 ` dpdklab
2024-09-05 0:46 ` dpdklab
2024-09-05 0:46 ` dpdklab
2024-09-05 0:46 ` dpdklab
2024-09-05 0:46 ` dpdklab
2024-09-05 0:47 ` dpdklab
2024-09-05 0:47 ` dpdklab
2024-09-05 0:47 ` dpdklab
2024-09-05 0:47 ` dpdklab
2024-09-05 0:47 ` dpdklab
2024-09-05 0:47 ` dpdklab
2024-09-05 0:47 ` dpdklab
2024-09-05 0:47 ` dpdklab
2024-09-05 0:48 ` dpdklab
2024-09-05 0:48 ` dpdklab
2024-09-05 0:48 ` dpdklab
2024-09-05 0:49 ` dpdklab
2024-09-05 0:50 ` dpdklab
2024-09-05 0:51 ` dpdklab
2024-09-05 0:51 ` dpdklab
2024-09-05 0:52 ` dpdklab
2024-09-05 0:52 ` dpdklab
2024-09-05 0:52 ` dpdklab
2024-09-05 0:52 ` dpdklab
2024-09-05 0:53 ` dpdklab
2024-09-05 0:56 ` dpdklab
2024-09-05 0:56 ` dpdklab
2024-09-05 0:57 ` dpdklab
2024-09-05 0:57 ` dpdklab
2024-09-05 0:57 ` dpdklab
2024-09-05 0:59 ` dpdklab
2024-09-05 1:02 ` dpdklab
2024-09-05 1:02 ` dpdklab
2024-09-05 1:03 ` dpdklab
2024-09-05 1:03 ` dpdklab
2024-09-05 1:03 ` dpdklab
2024-09-05 1:04 ` dpdklab
2024-09-05 1:06 ` dpdklab
2024-09-05 1:08 ` dpdklab
2024-09-05 2:45 ` dpdklab
2024-09-18 8:27 ` dpdklab
2024-09-18 8:46 ` dpdklab
2024-09-18 8:59 ` dpdklab
2024-09-18 9:30 ` 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=66d8b695.d40a0220.373053.0d15SMTPIN_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).