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| pw126059 [PATCH] examples/ipsec-secgw: fix AES-CTR IV length
Date: Fri, 14 Apr 2023 08:17:49 +0000 (UTC) [thread overview]
Message-ID: <20230414081749.7D7A060092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126059
_Testing PASS_
Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Friday, April 14 2023 04:35:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126059 --> testing pass
Test environment and result as below:
+---------------+----------+
| Environment | abi_test |
+===============+==========+
| Debian Buster | PASS |
+---------------+----------+
| RHEL8 | PASS |
+---------------+----------+
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25988/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-14 8:17 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 8:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-14 21:27 dpdklab
2023-04-14 21:23 dpdklab
2023-04-14 21:08 dpdklab
2023-04-14 21:03 dpdklab
2023-04-14 20:58 dpdklab
2023-04-14 20:53 dpdklab
2023-04-14 11:09 dpdklab
2023-04-14 10:19 dpdklab
2023-04-14 9:57 dpdklab
2023-04-14 9:57 dpdklab
2023-04-14 9:56 dpdklab
2023-04-14 9:49 dpdklab
2023-04-14 9:07 dpdklab
2023-04-14 9:02 dpdklab
2023-04-14 8:50 dpdklab
2023-04-14 8:50 dpdklab
2023-04-14 8:42 dpdklab
2023-04-14 8:39 dpdklab
2023-04-14 8:33 dpdklab
2023-04-14 8:33 dpdklab
2023-04-14 8:26 dpdklab
2023-04-14 8:22 dpdklab
2023-04-14 8:21 dpdklab
2023-04-14 8:20 dpdklab
2023-04-14 8:19 dpdklab
2023-04-14 8:03 dpdklab
2023-04-14 7:36 dpdklab
2023-04-14 7:35 dpdklab
2023-04-14 7:33 dpdklab
2023-04-14 7:33 dpdklab
2023-04-14 7:22 dpdklab
2023-04-14 7:21 dpdklab
2023-04-14 7:20 dpdklab
2023-04-14 7:20 dpdklab
2023-04-14 7:17 dpdklab
2023-04-14 7:16 dpdklab
2023-04-14 7:14 dpdklab
2023-04-14 7:11 dpdklab
2023-04-14 7:10 dpdklab
2023-04-14 7:04 dpdklab
2023-04-14 7:02 dpdklab
2023-04-14 6:58 dpdklab
2023-04-14 6:56 dpdklab
2023-04-14 6:55 dpdklab
2023-04-14 6:54 dpdklab
2023-04-14 6:53 dpdklab
2023-04-14 6:50 dpdklab
2023-04-14 6:48 dpdklab
2023-04-14 6:15 dpdklab
2023-04-14 6:11 dpdklab
2023-04-14 6:04 dpdklab
[not found] <20230414043545.784656-1-ktejasree@marvell.com>
2023-04-14 4:27 ` qemudev
2023-04-14 4:31 ` qemudev
2023-04-14 4:36 ` checkpatch
2023-04-14 5:59 ` 0-day Robot
2023-04-14 5:58 dpdklab
2023-04-14 5:57 dpdklab
2023-04-14 5:56 dpdklab
2023-04-14 5:55 dpdklab
2023-04-14 5:55 dpdklab
2023-04-14 5:51 dpdklab
2023-04-14 5:48 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=20230414081749.7D7A060092@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).