From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142125 [PATCH] crypto/qat: fix incorrect placement of oo
Date: Fri, 05 Jul 2024 02:49:56 -0700 (PDT) [thread overview]
Message-ID: <6687c1c4.050a0220.58ac9.212cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240704102649.30400-1-arkadiuszx.kusztal@intel.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142125
_Functional Testing PASS_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Thursday, July 04 2024 10:26:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ba268b0bb43b56174e3d9345a27e6b1675a5a991
142125 --> 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 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/30421/
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-05 9:49 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240704102649.30400-1-arkadiuszx.kusztal@intel.com>
2024-07-04 10:00 ` |SUCCESS| pw142125 [PATCH] crypto/qat: fix incorrect placement of oop offset qemudev
2024-07-04 10:05 ` qemudev
2024-07-04 10:27 ` checkpatch
2024-07-04 11:24 ` 0-day Robot
2024-07-04 13:59 ` |SUCCESS| pw142125 [PATCH] crypto/qat: fix incorrect placement of oo dpdklab
2024-07-04 14:27 ` dpdklab
2024-07-04 14:34 ` dpdklab
2024-07-04 14:49 ` dpdklab
2024-07-04 15:24 ` dpdklab
2024-07-04 17:32 ` |PENDING| " dpdklab
2024-07-04 17:35 ` dpdklab
2024-07-04 17:36 ` dpdklab
2024-07-04 17:39 ` dpdklab
2024-07-04 17:40 ` dpdklab
2024-07-04 17:42 ` dpdklab
2024-07-04 17:42 ` dpdklab
2024-07-04 17:49 ` dpdklab
2024-07-04 17:51 ` dpdklab
2024-07-04 17:52 ` dpdklab
2024-07-04 17:53 ` dpdklab
2024-07-04 17:59 ` dpdklab
2024-07-04 18:04 ` dpdklab
2024-07-04 18:05 ` dpdklab
2024-07-04 18:11 ` dpdklab
2024-07-04 19:44 ` |SUCCESS| " dpdklab
2024-07-05 0:19 ` dpdklab
2024-07-05 0:27 ` dpdklab
2024-07-05 1:03 ` dpdklab
2024-07-05 2:20 ` |PENDING| " dpdklab
2024-07-05 2:22 ` dpdklab
2024-07-05 2:23 ` dpdklab
2024-07-05 2:25 ` dpdklab
2024-07-05 2:28 ` dpdklab
2024-07-05 2:33 ` |SUCCESS| " dpdklab
2024-07-05 2:50 ` dpdklab
2024-07-05 4:36 ` |PENDING| " dpdklab
2024-07-05 9:35 ` |SUCCESS| " dpdklab
2024-07-05 9:49 ` dpdklab [this message]
2024-07-05 12:30 ` |PENDING| " dpdklab
2024-07-05 12:32 ` dpdklab
2024-07-05 12:39 ` dpdklab
2024-07-05 12:41 ` dpdklab
2024-07-05 12:43 ` dpdklab
2024-07-05 12:44 ` dpdklab
2024-07-05 12:47 ` dpdklab
2024-07-05 12:51 ` dpdklab
2024-07-05 12:56 ` dpdklab
2024-07-05 12:56 ` dpdklab
2024-07-05 13:00 ` dpdklab
2024-07-05 13:03 ` dpdklab
2024-07-05 13:04 ` dpdklab
2024-07-05 13:04 ` dpdklab
2024-07-05 13:09 ` dpdklab
2024-07-05 13:09 ` dpdklab
2024-07-05 13:11 ` |SUCCESS| " dpdklab
2024-07-05 13:11 ` dpdklab
2024-07-05 14:11 ` |PENDING| " dpdklab
2024-07-05 14:25 ` dpdklab
2024-07-05 14:26 ` dpdklab
2024-07-05 14:33 ` dpdklab
2024-07-05 14:35 ` dpdklab
2024-07-05 14:38 ` dpdklab
2024-07-05 14:39 ` dpdklab
2024-07-05 14:42 ` dpdklab
2024-07-05 14:47 ` dpdklab
2024-07-05 14:47 ` dpdklab
2024-07-05 14:49 ` dpdklab
2024-07-05 14:52 ` dpdklab
2024-07-05 14:56 ` dpdklab
2024-07-05 14:56 ` dpdklab
2024-07-05 14:56 ` dpdklab
2024-07-05 14:59 ` dpdklab
2024-07-05 15:01 ` dpdklab
2024-07-05 15:03 ` dpdklab
2024-07-05 15:13 ` |SUCCESS| " dpdklab
2024-07-05 17:10 ` |PENDING| " dpdklab
2024-07-05 17:13 ` dpdklab
2024-07-05 17:14 ` dpdklab
2024-07-05 17:17 ` dpdklab
2024-07-05 17:23 ` dpdklab
2024-07-05 17:28 ` dpdklab
2024-07-05 17:49 ` dpdklab
2024-07-05 17:56 ` dpdklab
2024-07-05 18:02 ` dpdklab
2024-07-05 18:03 ` dpdklab
2024-07-05 18:30 ` dpdklab
2024-07-05 18:46 ` dpdklab
2024-07-05 18:47 ` dpdklab
2024-07-05 18:48 ` dpdklab
2024-07-05 20:34 ` dpdklab
2024-07-05 20:37 ` dpdklab
2024-07-05 20:45 ` dpdklab
2024-07-05 20:53 ` dpdklab
2024-07-05 21:07 ` dpdklab
2024-07-05 21:16 ` dpdklab
2024-07-05 21:23 ` dpdklab
2024-07-05 21:49 ` dpdklab
2024-07-05 21:55 ` dpdklab
2024-07-05 21:56 ` dpdklab
2024-07-05 22:02 ` dpdklab
2024-07-05 22:11 ` dpdklab
2024-07-05 22:19 ` dpdklab
2024-07-05 22:21 ` dpdklab
2024-07-05 22:29 ` |SUCCESS| " dpdklab
2024-07-06 2:42 ` dpdklab
2024-07-06 13:31 ` dpdklab
2024-07-06 14:52 ` dpdklab
2024-07-06 15:08 ` dpdklab
2024-07-08 16:59 ` dpdklab
2024-07-08 17:12 ` 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=6687c1c4.050a0220.58ac9.212cSMTPIN_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).