From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133925 [PATCH] [v2] dumpcap: fix mbuf pool ring type
Date: Mon, 06 Nov 2023 12:38:36 -0800 (PST) [thread overview]
Message-ID: <65494ecc.050a0220.a5989.62dcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133925
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, November 06 2023 19:34:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70aef239d0de6b2048aecb1220da1d78edb75168
133925 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28259/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-06 20:38 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 20:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-06 23:30 dpdklab
2023-11-06 23:29 dpdklab
2023-11-06 22:33 dpdklab
2023-11-06 22:31 dpdklab
2023-11-06 22:07 dpdklab
2023-11-06 22:05 dpdklab
2023-11-06 21:58 dpdklab
2023-11-06 21:52 dpdklab
2023-11-06 21:47 dpdklab
2023-11-06 21:39 dpdklab
2023-11-06 21:33 dpdklab
2023-11-06 21:31 dpdklab
2023-11-06 21:18 dpdklab
2023-11-06 21:15 dpdklab
2023-11-06 21:06 dpdklab
2023-11-06 21:06 dpdklab
2023-11-06 21:05 dpdklab
2023-11-06 21:00 dpdklab
2023-11-06 20:56 dpdklab
2023-11-06 20:53 dpdklab
2023-11-06 20:51 dpdklab
2023-11-06 20:51 dpdklab
2023-11-06 20:49 dpdklab
2023-11-06 20:45 dpdklab
2023-11-06 20:44 dpdklab
2023-11-06 20:42 dpdklab
2023-11-06 20:41 dpdklab
2023-11-06 20:41 dpdklab
2023-11-06 20:39 dpdklab
2023-11-06 20:39 dpdklab
2023-11-06 20:39 dpdklab
2023-11-06 20:38 dpdklab
2023-11-06 20:38 dpdklab
2023-11-06 20:38 dpdklab
2023-11-06 20:37 dpdklab
2023-11-06 20:37 dpdklab
2023-11-06 20:37 dpdklab
2023-11-06 20:36 dpdklab
2023-11-06 20:36 dpdklab
2023-11-06 20:36 dpdklab
2023-11-06 20:36 dpdklab
2023-11-06 20:36 dpdklab
2023-11-06 20:35 dpdklab
2023-11-06 20:35 dpdklab
2023-11-06 20:35 dpdklab
2023-11-06 20:34 dpdklab
2023-11-06 20:34 dpdklab
2023-11-06 20:33 dpdklab
2023-11-06 20:33 dpdklab
2023-11-06 20:33 dpdklab
2023-11-06 20:32 dpdklab
2023-11-06 20:32 dpdklab
2023-11-06 20:32 dpdklab
2023-11-06 20:31 dpdklab
2023-11-06 20:31 dpdklab
2023-11-06 20:31 dpdklab
[not found] <20231106193423.12292-1-stephen@networkplumber.org>
2023-11-06 19:14 ` |SUCCESS| pw133925 [PATCH v2] " qemudev
2023-11-06 19:19 ` qemudev
2023-11-06 19:34 ` checkpatch
2023-11-06 20:59 ` 0-day Robot
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=65494ecc.050a0220.a5989.62dcSMTPIN_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).