From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137432-137434 [PATCH] [v6,4/4] test/cryptodev: add tests
Date: Wed, 28 Feb 2024 08:34:09 -0800 (PST) [thread overview]
Message-ID: <65df6081.050a0220.e3578.a3dcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228140036.1996629-5-nishikanta.nayak@intel.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137434
_Functional Testing PASS_
Submitter: Nishikant Nayak <nishikanta.nayak@intel.com>
Date: Wednesday, February 28 2024 14:00:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137432-137434 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29317/
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-02-28 16:34 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240228140036.1996629-5-nishikanta.nayak@intel.com>
2024-02-28 13:38 ` |SUCCESS| pw137432-137434 [PATCH v6 4/4] test/cryptodev: add tests for GCM with AAD qemudev
2024-02-28 13:42 ` qemudev
2024-02-28 14:02 ` |SUCCESS| pw137434 " checkpatch
2024-02-28 15:05 ` 0-day Robot
2024-02-28 16:17 ` |SUCCESS| pw137432-137434 [PATCH] [v6,4/4] test/cryptodev: add tests dpdklab
2024-02-28 16:33 ` dpdklab
2024-02-28 16:33 ` dpdklab
2024-02-28 16:33 ` dpdklab
2024-02-28 16:34 ` dpdklab [this message]
2024-02-28 16:34 ` dpdklab
2024-02-28 16:35 ` dpdklab
2024-02-28 16:35 ` dpdklab
2024-02-28 16:35 ` dpdklab
2024-02-28 16:35 ` dpdklab
2024-02-28 16:36 ` dpdklab
2024-02-28 16:36 ` dpdklab
2024-02-28 16:36 ` dpdklab
2024-02-28 16:36 ` dpdklab
2024-02-28 16:36 ` dpdklab
2024-02-28 16:37 ` dpdklab
2024-02-28 16:37 ` dpdklab
2024-02-28 16:37 ` dpdklab
2024-02-28 16:37 ` dpdklab
2024-02-28 16:38 ` dpdklab
2024-02-28 16:38 ` dpdklab
2024-02-28 16:38 ` dpdklab
2024-02-28 16:38 ` dpdklab
2024-02-28 16:38 ` dpdklab
2024-02-28 16:38 ` dpdklab
2024-02-28 16:39 ` dpdklab
2024-02-28 16:39 ` dpdklab
2024-02-28 16:39 ` dpdklab
2024-02-28 16:40 ` dpdklab
2024-02-28 16:40 ` dpdklab
2024-02-28 16:40 ` dpdklab
2024-02-28 16:41 ` dpdklab
2024-02-28 16:41 ` dpdklab
2024-02-28 16:41 ` dpdklab
2024-02-28 16:41 ` dpdklab
2024-02-28 16:42 ` dpdklab
2024-02-28 16:42 ` dpdklab
2024-02-28 16:42 ` dpdklab
2024-02-28 16:42 ` dpdklab
2024-02-28 16:42 ` dpdklab
2024-02-28 16:42 ` dpdklab
2024-02-28 16:42 ` dpdklab
2024-02-28 16:43 ` dpdklab
2024-02-28 16:43 ` dpdklab
2024-02-28 16:43 ` dpdklab
2024-02-28 16:44 ` dpdklab
2024-02-28 16:44 ` dpdklab
2024-02-28 16:44 ` dpdklab
2024-02-28 16:44 ` dpdklab
2024-02-28 16:44 ` dpdklab
2024-02-28 16:45 ` dpdklab
2024-02-28 16:45 ` dpdklab
2024-02-28 16:45 ` dpdklab
2024-02-28 16:46 ` dpdklab
2024-02-28 16:51 ` dpdklab
2024-02-28 16:55 ` dpdklab
2024-02-28 16:57 ` dpdklab
2024-02-28 17:44 ` dpdklab
2024-02-28 17:58 ` dpdklab
2024-02-28 18:56 ` dpdklab
2024-02-28 21:42 ` dpdklab
2024-02-28 21:49 ` dpdklab
2024-02-29 15:36 ` dpdklab
2024-02-29 23:49 ` dpdklab
2024-02-29 23:51 ` dpdklab
2024-02-29 23:59 ` dpdklab
2024-03-01 0:05 ` dpdklab
2024-03-02 1:02 ` dpdklab
2024-03-02 1:19 ` dpdklab
2024-03-02 1:52 ` 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=65df6081.050a0220.e3578.a3dcSMTPIN_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).