From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142665 [PATCH] doc: announce rte_ipsec API changes
Date: Tue, 23 Jul 2024 10:25:33 -0700 (PDT) [thread overview]
Message-ID: <669fe78d.170a0220.20a66f.22b7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240723130254.2128028-1-asasidharan@marvell.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142665
_Functional Testing PASS_
Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Tuesday, July 23 2024 13:02:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7d8c608faa7fb65345b0029a80251ecaa1a7c556
142665 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#170060
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| unit_tests_mbuf | PASS |
+-----------------+--------+
| mtu_update | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30593/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-07-23 17:25 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240723130254.2128028-1-asasidharan@marvell.com>
2024-07-23 12:36 ` qemudev
2024-07-23 12:41 ` qemudev
2024-07-23 13:04 ` |WARNING| " checkpatch
2024-07-23 14:03 ` |SUCCESS| " 0-day Robot
2024-07-23 17:14 ` dpdklab
2024-07-23 17:16 ` dpdklab
2024-07-23 17:17 ` dpdklab
2024-07-23 17:25 ` dpdklab [this message]
2024-07-23 17:27 ` dpdklab
2024-07-23 17:32 ` dpdklab
2024-07-23 17:38 ` dpdklab
2024-07-23 18:19 ` |PENDING| " dpdklab
2024-07-23 18:27 ` |SUCCESS| " dpdklab
2024-07-23 18:30 ` |PENDING| " dpdklab
2024-07-23 18:34 ` dpdklab
2024-07-23 18:38 ` dpdklab
2024-07-23 18:42 ` dpdklab
2024-07-23 18:43 ` dpdklab
2024-07-23 18:44 ` dpdklab
2024-07-23 18:48 ` dpdklab
2024-07-23 18:48 ` dpdklab
2024-07-23 18:51 ` dpdklab
2024-07-23 18:53 ` dpdklab
2024-07-23 18:54 ` dpdklab
2024-07-23 18:55 ` dpdklab
2024-07-23 18:55 ` dpdklab
2024-07-23 18:58 ` dpdklab
2024-07-23 18:58 ` dpdklab
2024-07-23 19:01 ` dpdklab
2024-07-23 19:02 ` dpdklab
2024-07-23 19:03 ` dpdklab
2024-07-23 19:03 ` dpdklab
2024-07-23 19:05 ` dpdklab
2024-07-23 19:11 ` dpdklab
2024-07-23 19:11 ` dpdklab
2024-07-23 19:14 ` dpdklab
2024-07-23 19:20 ` dpdklab
2024-07-23 19:21 ` dpdklab
2024-07-23 19:22 ` dpdklab
2024-07-23 19:24 ` dpdklab
2024-07-23 19:26 ` dpdklab
2024-07-23 19:26 ` dpdklab
2024-07-23 19:27 ` dpdklab
2024-07-23 19:29 ` dpdklab
2024-07-23 19:29 ` dpdklab
2024-07-23 19:33 ` dpdklab
2024-07-23 19:33 ` dpdklab
2024-07-23 19:34 ` dpdklab
2024-07-23 19:35 ` dpdklab
2024-07-23 19:35 ` dpdklab
2024-07-23 19:36 ` dpdklab
2024-07-23 19:38 ` dpdklab
2024-07-23 19:40 ` dpdklab
2024-07-23 19:42 ` dpdklab
2024-07-23 19:44 ` dpdklab
2024-07-23 19:46 ` dpdklab
2024-07-23 19:47 ` dpdklab
2024-07-23 19:51 ` dpdklab
2024-07-23 19:55 ` dpdklab
2024-07-23 19:56 ` dpdklab
2024-07-23 19:57 ` dpdklab
2024-07-23 19:58 ` |SUCCESS| " dpdklab
2024-07-23 20:05 ` |PENDING| " dpdklab
2024-07-23 20:06 ` dpdklab
2024-07-23 20:20 ` |SUCCESS| " dpdklab
2024-07-23 20:25 ` dpdklab
2024-07-23 20:26 ` |PENDING| " dpdklab
2024-07-23 20:29 ` |SUCCESS| " dpdklab
2024-07-23 20:31 ` |PENDING| " dpdklab
2024-07-23 20:32 ` dpdklab
2024-07-23 20:34 ` |SUCCESS| " dpdklab
2024-07-23 20:36 ` |PENDING| " dpdklab
2024-07-23 20:40 ` dpdklab
2024-07-23 20:41 ` |SUCCESS| " dpdklab
2024-07-23 20:46 ` |PENDING| " dpdklab
2024-07-23 20:47 ` dpdklab
2024-07-23 20:51 ` dpdklab
2024-07-23 20:51 ` dpdklab
2024-07-23 20:52 ` dpdklab
2024-07-23 20:52 ` dpdklab
2024-07-23 20:52 ` |SUCCESS| " dpdklab
2024-07-23 20:56 ` |PENDING| " dpdklab
2024-07-23 20:57 ` dpdklab
2024-07-23 20:57 ` dpdklab
2024-07-23 21:01 ` dpdklab
2024-07-23 21:02 ` dpdklab
2024-07-23 21:08 ` dpdklab
2024-07-23 21:08 ` |SUCCESS| " dpdklab
2024-07-23 21:11 ` |PENDING| " dpdklab
2024-07-23 21:16 ` dpdklab
2024-07-23 21:22 ` dpdklab
2024-07-23 21:22 ` dpdklab
2024-07-23 21:23 ` dpdklab
2024-07-23 21:26 ` dpdklab
2024-07-23 21:27 ` dpdklab
2024-07-23 21:28 ` dpdklab
2024-07-23 21:29 ` dpdklab
2024-07-23 21:30 ` dpdklab
2024-07-23 21:33 ` dpdklab
2024-07-23 21:34 ` dpdklab
2024-07-23 21:35 ` dpdklab
2024-07-23 21:36 ` dpdklab
2024-07-23 21:38 ` dpdklab
2024-07-23 21:42 ` dpdklab
2024-07-23 21:44 ` |SUCCESS| " dpdklab
2024-07-23 21:46 ` |PENDING| " dpdklab
2024-07-23 21:51 ` dpdklab
2024-07-23 21:58 ` dpdklab
2024-07-23 22:07 ` dpdklab
2024-07-25 0:08 ` |SUCCESS| " 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=669fe78d.170a0220.20a66f.22b7SMTPIN_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).