From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 2b551097b3443ebf662e4d140600a4c9b108e73c
Date: Thu, 01 Feb 2024 13:16:59 -0800 (PST) [thread overview]
Message-ID: <65bc0a4b.920a0220.30730.198cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-crypto
2b551097b3443ebf662e4d140600a4c9b108e73c --> testing pass
Test environment and result as below:
+-----------------------+----------------+
| Environment | dpdk_unit_test |
+=======================+================+
| CentOS Stream 9 (ARM) | PASS |
+-----------------------+----------------+
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27871/
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-01 21:17 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 21:16 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 22:37 dpdklab
2024-02-01 22:26 dpdklab
2024-02-01 21:53 dpdklab
2024-02-01 21:52 dpdklab
2024-02-01 21:45 dpdklab
2024-02-01 21:44 dpdklab
2024-02-01 21:44 dpdklab
2024-02-01 21:43 dpdklab
2024-02-01 21:41 dpdklab
2024-02-01 21:41 dpdklab
2024-02-01 21:37 dpdklab
2024-02-01 21:35 dpdklab
2024-02-01 21:35 dpdklab
2024-02-01 21:34 dpdklab
2024-02-01 21:33 dpdklab
2024-02-01 21:32 dpdklab
2024-02-01 21:26 dpdklab
2024-02-01 21:26 dpdklab
2024-02-01 21:25 dpdklab
2024-02-01 21:25 dpdklab
2024-02-01 21:24 dpdklab
2024-02-01 21:22 dpdklab
2024-02-01 21:22 dpdklab
2024-02-01 21:22 dpdklab
2024-02-01 21:20 dpdklab
2024-02-01 21:17 dpdklab
2024-02-01 21:16 dpdklab
2024-02-01 21:15 dpdklab
2024-02-01 21:15 dpdklab
2024-02-01 21:14 dpdklab
2024-02-01 21:14 dpdklab
2024-02-01 21:13 dpdklab
2024-02-01 21:13 dpdklab
2024-02-01 21:13 dpdklab
2024-02-01 21:12 dpdklab
2024-02-01 21:12 dpdklab
2024-02-01 21:12 dpdklab
2024-02-01 21:12 dpdklab
2024-02-01 21:11 dpdklab
2024-02-01 21:10 dpdklab
2024-02-01 21:09 dpdklab
2024-02-01 21:08 dpdklab
2024-02-01 21:08 dpdklab
2024-02-01 21:07 dpdklab
2024-02-01 21:07 dpdklab
2024-02-01 21:06 dpdklab
2024-02-01 21:05 dpdklab
2024-02-01 21:05 dpdklab
2024-02-01 21:04 dpdklab
2024-02-01 21:03 dpdklab
2024-02-01 21:01 dpdklab
2024-02-01 20:59 dpdklab
2024-02-01 20:52 dpdklab
2024-02-01 20:51 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=65bc0a4b.920a0220.30730.198cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=gakhil@marvell.com \
--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).