From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw151128 [PATCH] examples/ipsec-secgw: fix iv len in ctr 1
Date: Sat, 08 Feb 2025 01:59:57 -0800 (PST) [thread overview]
Message-ID: <67a72b1d.050a0220.30c7bb.d55eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250207134545.63820-1-nkaithakadan@marvell.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/151128
_Functional Testing PASS_
Submitter: Nithinsen Kaithakadan <nkaithakadan@marvell.com>
Date: Friday, February 07 2025 13:45:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:388b1abe291544106e406cb0a200b5b0c96fe599
151128 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#211511
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-131-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32524/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-02-08 9:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250207134545.63820-1-nkaithakadan@marvell.com>
2025-02-07 13:14 ` |SUCCESS| pw151128 [PATCH] examples/ipsec-secgw: fix iv len in ctr 192/256 qemudev
2025-02-07 13:20 ` |FAILURE| " qemudev
2025-02-07 13:45 ` |SUCCESS| " checkpatch
2025-02-07 14:45 ` 0-day Robot
2025-02-07 18:31 ` |SUCCESS| pw151128 [PATCH] examples/ipsec-secgw: fix iv len in ctr 1 dpdklab
2025-02-07 18:32 ` dpdklab
2025-02-07 19:15 ` dpdklab
2025-02-07 19:15 ` dpdklab
2025-02-07 20:06 ` dpdklab
2025-02-07 20:10 ` dpdklab
2025-02-07 20:11 ` dpdklab
2025-02-07 20:12 ` dpdklab
2025-02-07 20:21 ` dpdklab
2025-02-07 20:27 ` dpdklab
2025-02-07 20:36 ` |PENDING| " dpdklab
2025-02-07 20:39 ` dpdklab
2025-02-07 20:54 ` dpdklab
2025-02-07 20:54 ` dpdklab
2025-02-07 21:28 ` dpdklab
2025-02-07 21:35 ` dpdklab
2025-02-07 21:41 ` |SUCCESS| " dpdklab
2025-02-07 21:48 ` |PENDING| " dpdklab
2025-02-07 22:01 ` dpdklab
2025-02-07 22:22 ` |SUCCESS| " dpdklab
2025-02-07 22:34 ` dpdklab
2025-02-07 22:34 ` dpdklab
2025-02-07 23:24 ` dpdklab
2025-02-07 23:24 ` dpdklab
2025-02-07 23:25 ` dpdklab
2025-02-07 23:26 ` dpdklab
2025-02-08 0:18 ` dpdklab
2025-02-08 1:06 ` |WARNING| " dpdklab
2025-02-08 1:14 ` dpdklab
2025-02-08 2:02 ` dpdklab
2025-02-08 2:17 ` |SUCCESS| " dpdklab
2025-02-08 3:11 ` dpdklab
2025-02-08 7:58 ` dpdklab
2025-02-08 9:20 ` dpdklab
2025-02-08 9:59 ` dpdklab [this message]
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=67a72b1d.050a0220.30c7bb.d55eSMTPIN_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).