From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124807 [PATCH] app/test: fix data length of each packet segment
Date: Sun, 5 Mar 2023 23:56:13 +0000 (UTC) [thread overview]
Message-ID: <20230305235613.F3B2160095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/124807
_Testing PASS_
Submitter: Zhuobin Huang <zobin1999@gmail.com>
Date: Sunday, March 05 2023 21:07:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124807 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25617/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-05 23:56 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 23:56 dpdklab [this message]
[not found] <20230305210723.15653-1-zobin1999@gmail.com>
2023-03-05 22:59 ` 0-day Robot
2023-03-06 6:57 ` qemudev
2023-03-06 6:57 ` qemudev
-- strict thread matches above, loose matches on Subject: below --
2023-03-06 6:30 dpdklab
2023-03-06 6:25 dpdklab
2023-03-06 6:22 dpdklab
2023-03-06 6:11 dpdklab
2023-03-06 6:07 dpdklab
2023-03-06 5:56 dpdklab
2023-03-06 1:53 dpdklab
2023-03-06 1:20 dpdklab
2023-03-06 1:20 dpdklab
2023-03-06 1:10 dpdklab
2023-03-06 0:57 dpdklab
2023-03-06 0:51 dpdklab
2023-03-06 0:49 dpdklab
2023-03-06 0:47 dpdklab
2023-03-06 0:44 dpdklab
2023-03-06 0:41 dpdklab
2023-03-06 0:39 dpdklab
2023-03-06 0:34 dpdklab
2023-03-06 0:25 dpdklab
2023-03-06 0:18 dpdklab
2023-03-06 0:16 dpdklab
2023-03-06 0:13 dpdklab
2023-03-06 0:05 dpdklab
2023-03-06 0:05 dpdklab
2023-03-06 0:05 dpdklab
2023-03-06 0:04 dpdklab
2023-03-06 0:01 dpdklab
2023-03-05 23:58 dpdklab
2023-03-05 23:58 dpdklab
2023-03-05 23:52 dpdklab
2023-03-05 23:50 dpdklab
2023-03-05 23:49 dpdklab
2023-03-05 23:48 dpdklab
2023-03-05 23:48 dpdklab
2023-03-05 23:47 dpdklab
2023-03-05 23:40 dpdklab
2023-03-05 23:37 dpdklab
2023-03-05 23:30 dpdklab
2023-03-05 23:17 dpdklab
2023-03-05 23:15 dpdklab
2023-03-05 23:10 dpdklab
2023-03-05 23:03 dpdklab
2023-03-05 23:02 dpdklab
2023-03-05 22:58 dpdklab
2023-03-05 22:50 dpdklab
2023-03-05 22:46 dpdklab
2023-03-05 22:45 dpdklab
2023-03-05 22:40 dpdklab
2023-03-05 22:38 dpdklab
2023-03-05 22:33 dpdklab
2023-03-05 22:33 dpdklab
2023-03-05 22:31 dpdklab
2023-03-05 22:30 dpdklab
2023-03-05 22:26 dpdklab
2023-03-05 22:25 dpdklab
2023-03-05 22:23 dpdklab
2023-03-05 22:18 dpdklab
2023-03-05 22:17 dpdklab
2023-03-05 22:13 dpdklab
2023-03-05 22:13 dpdklab
2023-03-05 22:07 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=20230305235613.F3B2160095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).