From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131454 [PATCH] testpmd: unregister event callback
Date: Thu, 14 Sep 2023 22:13:34 -0700 (PDT) [thread overview]
Message-ID: <6503e7fe.810a0220.6e581.dc0eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131454
_Testing PASS_
Submitter: Sinan Kaya <okaya@kernel.org>
Date: Friday, September 15 2023 04:26:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e92ba1426914db1d224dd5e9a1743657681b8814
131454 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27611/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-15 5:13 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 5:13 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-15 6:14 dpdklab
2023-09-15 5:28 dpdklab
2023-09-15 5:24 dpdklab
2023-09-15 5:24 dpdklab
2023-09-15 5:21 dpdklab
2023-09-15 5:21 dpdklab
2023-09-15 5:17 dpdklab
2023-09-15 5:17 dpdklab
2023-09-15 5:14 dpdklab
2023-09-15 5:12 dpdklab
2023-09-15 5:12 dpdklab
2023-09-15 5:11 dpdklab
2023-09-15 5:10 dpdklab
2023-09-15 5:10 dpdklab
2023-09-15 5:07 dpdklab
2023-09-15 5:07 dpdklab
2023-09-15 5:06 dpdklab
2023-09-15 5:05 dpdklab
2023-09-15 5:05 dpdklab
2023-09-15 5:04 dpdklab
2023-09-15 5:04 dpdklab
2023-09-15 5:04 dpdklab
2023-09-15 5:04 dpdklab
2023-09-15 5:04 dpdklab
2023-09-15 5:03 dpdklab
2023-09-15 5:03 dpdklab
2023-09-15 5:03 dpdklab
2023-09-15 5:03 dpdklab
2023-09-15 5:03 dpdklab
2023-09-15 5:03 dpdklab
2023-09-15 5:03 dpdklab
2023-09-15 5:02 dpdklab
2023-09-15 5:02 dpdklab
2023-09-15 5:02 dpdklab
2023-09-15 5:02 dpdklab
2023-09-15 5:02 dpdklab
2023-09-15 5:01 dpdklab
2023-09-15 5:01 dpdklab
2023-09-15 5:01 dpdklab
2023-09-15 5:00 dpdklab
2023-09-15 5:00 dpdklab
2023-09-15 5:00 dpdklab
2023-09-15 4:59 dpdklab
2023-09-15 4:59 dpdklab
2023-09-15 4:59 dpdklab
2023-09-15 4:59 dpdklab
[not found] <20230915042633.151750-1-okaya@kernel.org>
2023-09-15 4:08 ` qemudev
2023-09-15 4:12 ` qemudev
2023-09-15 4:28 ` checkpatch
2023-09-15 5:19 ` 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=6503e7fe.810a0220.6e581.dc0eSMTPIN_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).