From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136204 [PATCH] [v2] net/mana: use rte_pktmbuf_alloc_bulk
Date: Mon, 29 Jan 2024 18:24:47 -0800 (PST) [thread overview]
Message-ID: <65b85def.d40a0220.8e9b5.4e11SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136204
_Testing PASS_
Submitter: Long Li <longli@linuxonhyperv.com>
Date: Tuesday, January 30 2024 01:13:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:906d2c06b3cfc61620453c6909266fe771f8ccfb
136204 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | 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
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28981/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-30 2:24 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 2:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 3:38 dpdklab
2024-01-30 3:32 dpdklab
2024-01-30 3:29 dpdklab
2024-01-30 3:26 dpdklab
2024-01-30 3:15 dpdklab
2024-01-30 3:14 dpdklab
2024-01-30 3:01 dpdklab
2024-01-30 3:00 dpdklab
2024-01-30 2:45 dpdklab
2024-01-30 2:42 dpdklab
2024-01-30 2:39 dpdklab
2024-01-30 2:39 dpdklab
2024-01-30 2:38 dpdklab
2024-01-30 2:38 dpdklab
2024-01-30 2:35 dpdklab
2024-01-30 2:34 dpdklab
2024-01-30 2:34 dpdklab
2024-01-30 2:31 dpdklab
2024-01-30 2:30 dpdklab
2024-01-30 2:30 dpdklab
2024-01-30 2:26 dpdklab
2024-01-30 2:26 dpdklab
2024-01-30 2:25 dpdklab
2024-01-30 2:21 dpdklab
2024-01-30 2:21 dpdklab
2024-01-30 2:19 dpdklab
2024-01-30 2:18 dpdklab
2024-01-30 2:18 dpdklab
2024-01-30 2:17 dpdklab
2024-01-30 2:17 dpdklab
2024-01-30 2:17 dpdklab
2024-01-30 2:17 dpdklab
2024-01-30 2:16 dpdklab
2024-01-30 2:16 dpdklab
2024-01-30 2:15 dpdklab
2024-01-30 2:14 dpdklab
2024-01-30 2:11 dpdklab
2024-01-30 2:10 dpdklab
2024-01-30 2:10 dpdklab
2024-01-30 2:09 dpdklab
2024-01-30 2:09 dpdklab
2024-01-30 2:09 dpdklab
2024-01-30 2:04 dpdklab
2024-01-30 2:04 dpdklab
2024-01-30 2:03 dpdklab
2024-01-30 2:03 dpdklab
2024-01-30 2:03 dpdklab
2024-01-30 2:02 dpdklab
2024-01-30 2:01 dpdklab
2024-01-30 2:01 dpdklab
2024-01-30 2:01 dpdklab
2024-01-30 2:00 dpdklab
2024-01-30 2:00 dpdklab
2024-01-30 2:00 dpdklab
2024-01-30 2:00 dpdklab
2024-01-30 1:59 dpdklab
2024-01-30 1:59 dpdklab
2024-01-30 1:58 dpdklab
2024-01-30 1:58 dpdklab
2024-01-30 1:58 dpdklab
2024-01-30 1:58 dpdklab
2024-01-30 1:57 dpdklab
2024-01-30 1:57 dpdklab
2024-01-30 1:57 dpdklab
2024-01-30 1:57 dpdklab
2024-01-30 1:56 dpdklab
2024-01-30 1:56 dpdklab
2024-01-30 1:55 dpdklab
2024-01-30 1:55 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=65b85def.d40a0220.8e9b5.4e11SMTPIN_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).