From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136251 [PATCH] [v3] net/mana: use rte_pktmbuf_alloc_bulk
Date: Wed, 31 Jan 2024 21:00:50 -0800 (PST) [thread overview]
Message-ID: <65bb2582.0d0a0220.402fa.f728SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136251
_Testing PASS_
Submitter: Long Li <longli@linuxonhyperv.com>
Date: Thursday, February 01 2024 03:45:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8e5cbd3d1f6f077abdcb2ef4de027603ba9af5ca
136251 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29010/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-01 5:00 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 5:00 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 6:14 dpdklab
2024-02-01 5:36 dpdklab
2024-02-01 5:28 dpdklab
2024-02-01 5:01 dpdklab
2024-02-01 5:00 dpdklab
2024-02-01 4:58 dpdklab
2024-02-01 4:58 dpdklab
2024-02-01 4:57 dpdklab
2024-02-01 4:56 dpdklab
2024-02-01 4:56 dpdklab
2024-02-01 4:56 dpdklab
2024-02-01 4:55 dpdklab
2024-02-01 4:54 dpdklab
2024-02-01 4:54 dpdklab
2024-02-01 4:54 dpdklab
2024-02-01 4:53 dpdklab
2024-02-01 4:53 dpdklab
2024-02-01 4:53 dpdklab
2024-02-01 4:52 dpdklab
2024-02-01 4:52 dpdklab
2024-02-01 4:51 dpdklab
2024-02-01 4:51 dpdklab
2024-02-01 4:51 dpdklab
2024-02-01 4:50 dpdklab
2024-02-01 4:50 dpdklab
2024-02-01 4:50 dpdklab
2024-02-01 4:49 dpdklab
2024-02-01 4:49 dpdklab
2024-02-01 4:49 dpdklab
2024-02-01 4:48 dpdklab
2024-02-01 4:48 dpdklab
2024-02-01 4:43 dpdklab
2024-02-01 4:42 dpdklab
2024-02-01 4:37 dpdklab
2024-02-01 4:37 dpdklab
2024-02-01 4:36 dpdklab
2024-02-01 4:36 dpdklab
2024-02-01 4:35 dpdklab
2024-02-01 4:35 dpdklab
2024-02-01 4:35 dpdklab
2024-02-01 4:35 dpdklab
2024-02-01 4:35 dpdklab
2024-02-01 4:34 dpdklab
2024-02-01 4:34 dpdklab
2024-02-01 4:33 dpdklab
2024-02-01 4:31 dpdklab
2024-02-01 4:31 dpdklab
2024-02-01 4:31 dpdklab
2024-02-01 4:31 dpdklab
2024-02-01 4:30 dpdklab
2024-02-01 4:27 dpdklab
2024-02-01 4:27 dpdklab
2024-02-01 4:27 dpdklab
2024-02-01 4:26 dpdklab
2024-02-01 4:26 dpdklab
2024-02-01 4:25 dpdklab
2024-02-01 4:25 dpdklab
2024-02-01 4:25 dpdklab
2024-02-01 4:24 dpdklab
2024-02-01 4:24 dpdklab
2024-02-01 4:24 dpdklab
2024-02-01 4:24 dpdklab
2024-02-01 4:24 dpdklab
2024-02-01 4:23 dpdklab
2024-02-01 4:23 dpdklab
2024-02-01 4:23 dpdklab
2024-02-01 4:22 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=65bb2582.0d0a0220.402fa.f728SMTPIN_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).