From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137201-137204 [PATCH] [v2,4/4] test/cryptodev: add tests
Date: Mon, 26 Feb 2024 10:36:29 -0800 (PST) [thread overview]
Message-ID: <65dcda2d.4a0a0220.fcc48.5a93SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137204
_Functional Testing PASS_
Submitter: Nishikant Nayak <nishikanta.nayak@intel.com>
Date: Monday, February 26 2024 13:03:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137201-137204 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29263/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-26 18:36 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 18:36 dpdklab [this message]
[not found] <20240226130342.4115292-5-nishikanta.nayak@intel.com>
2024-02-28 1:29 ` dpdklab
2024-02-28 1:40 ` dpdklab
2024-02-28 2:10 ` dpdklab
2024-02-28 2:16 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-26 18:19 dpdklab
2024-02-26 17:50 dpdklab
2024-02-26 15:15 dpdklab
2024-02-26 15:14 dpdklab
2024-02-26 14:56 dpdklab
2024-02-26 14:45 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:31 dpdklab
2024-02-26 14:31 dpdklab
2024-02-26 14:30 dpdklab
2024-02-26 14:29 dpdklab
2024-02-26 14:27 dpdklab
2024-02-26 14:25 dpdklab
2024-02-26 14:14 dpdklab
2024-02-26 14:13 dpdklab
2024-02-26 14:13 dpdklab
2024-02-26 14:13 dpdklab
2024-02-26 14:13 dpdklab
2024-02-26 14:12 dpdklab
2024-02-26 14:11 dpdklab
2024-02-26 14:09 dpdklab
2024-02-26 14:09 dpdklab
2024-02-26 14:08 dpdklab
2024-02-26 14:08 dpdklab
2024-02-26 14:08 dpdklab
2024-02-26 14:07 dpdklab
2024-02-26 14:07 dpdklab
2024-02-26 14:06 dpdklab
2024-02-26 14:06 dpdklab
2024-02-26 14:06 dpdklab
2024-02-26 14:05 dpdklab
2024-02-26 14:04 dpdklab
2024-02-26 14:04 dpdklab
2024-02-26 14:04 dpdklab
2024-02-26 14:04 dpdklab
2024-02-26 14:03 dpdklab
2024-02-26 14:03 dpdklab
2024-02-26 14:03 dpdklab
2024-02-26 14:02 dpdklab
2024-02-26 14:02 dpdklab
2024-02-26 14:02 dpdklab
2024-02-26 13:58 dpdklab
2024-02-26 13:58 dpdklab
2024-02-26 13:57 dpdklab
2024-02-26 13:57 dpdklab
2024-02-26 13:56 dpdklab
2024-02-26 13:56 dpdklab
2024-02-26 13:56 dpdklab
2024-02-26 13:55 dpdklab
2024-02-26 13:54 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=65dcda2d.4a0a0220.fcc48.5a93SMTPIN_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).