From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142016 [PATCH] driver: crypto: scheduler: fix session si
Date: Tue, 02 Jul 2024 18:11:08 -0700 (PDT) [thread overview]
Message-ID: <6684a52c.170a0220.77584.5de5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240702075052.1697714-1-jhascoet@kalrayinc.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142016
_Functional Testing PASS_
Submitter: jhascoet <ju.hascoet@gmail.com>
Date: Tuesday, July 02 2024 07:50:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:22753c9544232e547584c9917572cd05cc29bec6
142016 --> functional testing pass
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
Target: Unknown
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | 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
Target: Unknown
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | 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
Target: Unknown
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/30375/
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-03 1:11 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240702075052.1697714-1-jhascoet@kalrayinc.com>
2024-07-02 8:15 ` |SUCCESS| pw142016 [PATCH] driver: crypto: scheduler: fix session size computation qemudev
2024-07-02 8:19 ` qemudev
2024-07-02 8:42 ` |WARNING| " checkpatch
2024-07-02 9:45 ` |SUCCESS| " 0-day Robot
2024-07-03 0:11 ` |SUCCESS| pw142016 [PATCH] driver: crypto: scheduler: fix session si dpdklab
2024-07-03 0:17 ` dpdklab
2024-07-03 1:11 ` dpdklab [this message]
2024-07-03 1:24 ` dpdklab
2024-07-03 2:59 ` dpdklab
2024-07-03 3:06 ` |PENDING| " dpdklab
2024-07-03 3:10 ` dpdklab
2024-07-03 3:15 ` dpdklab
2024-07-03 3:22 ` dpdklab
2024-07-03 3:23 ` dpdklab
2024-07-03 3:23 ` dpdklab
2024-07-03 3:25 ` dpdklab
2024-07-03 3:25 ` dpdklab
2024-07-03 3:32 ` dpdklab
2024-07-03 3:33 ` dpdklab
2024-07-03 3:35 ` |SUCCESS| " dpdklab
2024-07-03 3:35 ` |PENDING| " dpdklab
2024-07-03 3:36 ` dpdklab
2024-07-03 3:36 ` dpdklab
2024-07-03 3:37 ` dpdklab
2024-07-03 3:40 ` dpdklab
2024-07-03 3:41 ` |SUCCESS| " dpdklab
2024-07-03 3:41 ` |PENDING| " dpdklab
2024-07-03 3:45 ` |SUCCESS| " dpdklab
2024-07-03 3:49 ` |PENDING| " dpdklab
2024-07-03 3:53 ` |SUCCESS| " dpdklab
2024-07-03 4:48 ` |PENDING| " dpdklab
2024-07-03 5:17 ` |SUCCESS| " dpdklab
2024-07-03 5:36 ` dpdklab
2024-07-03 5:40 ` dpdklab
2024-07-03 5:49 ` dpdklab
2024-07-03 6:51 ` |PENDING| " dpdklab
2024-07-03 9:19 ` dpdklab
2024-07-03 9:21 ` dpdklab
2024-07-03 9:24 ` dpdklab
2024-07-03 9:27 ` dpdklab
2024-07-03 9:28 ` dpdklab
2024-07-03 9:29 ` dpdklab
2024-07-03 9:35 ` dpdklab
2024-07-03 9:35 ` dpdklab
2024-07-03 9:39 ` dpdklab
2024-07-03 9:41 ` dpdklab
2024-07-03 9:43 ` dpdklab
2024-07-03 9:44 ` dpdklab
2024-07-03 9:47 ` dpdklab
2024-07-03 9:49 ` dpdklab
2024-07-03 9:50 ` dpdklab
2024-07-03 10:02 ` dpdklab
2024-07-03 10:04 ` |SUCCESS| " dpdklab
2024-07-03 10:44 ` |PENDING| " dpdklab
2024-07-03 10:45 ` dpdklab
2024-07-03 10:48 ` dpdklab
2024-07-03 10:48 ` dpdklab
2024-07-03 10:49 ` dpdklab
2024-07-03 10:49 ` dpdklab
2024-07-03 10:50 ` dpdklab
2024-07-03 10:50 ` dpdklab
2024-07-03 10:52 ` dpdklab
2024-07-03 10:52 ` dpdklab
2024-07-03 10:53 ` dpdklab
2024-07-03 10:53 ` dpdklab
2024-07-03 10:55 ` dpdklab
2024-07-03 10:57 ` dpdklab
2024-07-03 10:57 ` dpdklab
2024-07-03 10:59 ` dpdklab
2024-07-03 11:00 ` dpdklab
2024-07-03 11:01 ` dpdklab
2024-07-03 11:10 ` dpdklab
2024-07-03 11:11 ` dpdklab
2024-07-03 11:12 ` dpdklab
2024-07-03 11:17 ` dpdklab
2024-07-03 11:21 ` dpdklab
2024-07-03 11:30 ` |SUCCESS| " dpdklab
2024-07-03 11:32 ` |PENDING| " dpdklab
2024-07-03 11:54 ` dpdklab
2024-07-03 12:09 ` dpdklab
2024-07-03 12:14 ` dpdklab
2024-07-03 12:24 ` dpdklab
2024-07-03 12:31 ` dpdklab
2024-07-03 12:36 ` dpdklab
2024-07-03 12:43 ` dpdklab
2024-07-03 12:43 ` dpdklab
2024-07-03 12:49 ` dpdklab
2024-07-03 12:55 ` |SUCCESS| " dpdklab
2024-07-03 14:12 ` dpdklab
2024-07-03 16:36 ` |PENDING| " dpdklab
2024-07-03 16:38 ` dpdklab
2024-07-03 16:46 ` dpdklab
2024-07-03 16:48 ` dpdklab
2024-07-03 17:01 ` dpdklab
2024-07-03 17:09 ` dpdklab
2024-07-03 17:18 ` dpdklab
2024-07-03 17:29 ` dpdklab
2024-07-03 17:37 ` dpdklab
2024-07-03 17:44 ` dpdklab
2024-07-03 17:54 ` dpdklab
2024-07-03 17:55 ` dpdklab
2024-07-03 18:02 ` dpdklab
2024-07-03 18:05 ` dpdklab
2024-07-03 18:10 ` dpdklab
2024-07-03 18:28 ` |SUCCESS| " dpdklab
2024-07-04 4:02 ` dpdklab
2024-07-04 5:37 ` 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=6684a52c.170a0220.77584.5de5SMTPIN_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).