From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Chaoyong He <chaoyong.he@corigine.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| pw135190-135192 [PATCH] [3/3] net/nfp: free domain ID in c
Date: Thu, 14 Dec 2023 04:19:42 -0800 (PST) [thread overview]
Message-ID: <657af2de.050a0220.9da9f.7f76SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135192
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thursday, December 14 2023 10:24:31
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:58bcca462447a4e184e0253438787db12dbb54ab
135190-135192 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28621/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-14 12:19 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 12:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-14 14:47 dpdklab
2023-12-14 14:40 dpdklab
2023-12-14 14:03 dpdklab
2023-12-14 13:34 dpdklab
2023-12-14 13:32 dpdklab
2023-12-14 13:22 dpdklab
2023-12-14 13:21 dpdklab
2023-12-14 13:19 dpdklab
2023-12-14 13:17 dpdklab
2023-12-14 13:17 dpdklab
2023-12-14 13:14 dpdklab
2023-12-14 13:10 dpdklab
2023-12-14 13:10 dpdklab
2023-12-14 12:58 dpdklab
2023-12-14 12:49 dpdklab
2023-12-14 12:49 dpdklab
2023-12-14 12:48 dpdklab
2023-12-14 12:40 dpdklab
2023-12-14 12:39 dpdklab
2023-12-14 12:39 dpdklab
2023-12-14 12:38 dpdklab
2023-12-14 12:37 dpdklab
2023-12-14 12:37 dpdklab
2023-12-14 12:35 dpdklab
2023-12-14 12:35 dpdklab
2023-12-14 12:35 dpdklab
2023-12-14 12:30 dpdklab
2023-12-14 12:29 dpdklab
2023-12-14 12:28 dpdklab
2023-12-14 12:28 dpdklab
2023-12-14 12:27 dpdklab
2023-12-14 12:26 dpdklab
2023-12-14 12:26 dpdklab
2023-12-14 12:25 dpdklab
2023-12-14 12:25 dpdklab
2023-12-14 12:25 dpdklab
2023-12-14 12:22 dpdklab
2023-12-14 12:19 dpdklab
2023-12-14 12:11 dpdklab
2023-12-14 12:11 dpdklab
2023-12-14 12:05 dpdklab
2023-12-14 12:04 dpdklab
2023-12-14 12:04 dpdklab
2023-12-14 12:04 dpdklab
2023-12-14 12:03 dpdklab
2023-12-14 12:02 dpdklab
2023-12-14 12:02 dpdklab
2023-12-14 12:01 dpdklab
2023-12-14 12:01 dpdklab
2023-12-14 12:00 dpdklab
2023-12-14 12:00 dpdklab
2023-12-14 11:59 dpdklab
2023-12-14 11:57 dpdklab
2023-12-14 11:42 dpdklab
2023-12-14 11:34 dpdklab
2023-12-14 11:34 dpdklab
2023-12-14 11:33 dpdklab
2023-12-14 11:26 dpdklab
2023-12-14 11:25 dpdklab
2023-12-14 11:24 dpdklab
2023-12-14 11:19 dpdklab
2023-12-14 11:18 dpdklab
2023-12-14 11:11 dpdklab
2023-12-14 11:10 dpdklab
2023-12-14 11:10 dpdklab
2023-12-14 11:07 dpdklab
2023-12-14 11:06 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=657af2de.050a0220.9da9f.7f76SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=chaoyong.he@corigine.com \
--cc=ferruh.yigit@amd.com \
--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).