From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 6a5507a4511afd0203d924a08517c55b35e6e74b
Date: Thu, 17 Aug 2023 11:36:47 -0700 (PDT) [thread overview]
Message-ID: <64de68bf.170a0220.b9604.781cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
6a5507a4511afd0203d924a08517c55b35e6e74b --> testing pass
Test environment and result as below:
+--------------------------+---------------------------+------------------------------+----------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+==========================+===========================+==============================+================+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+--------------------------+---------------------------+------------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+---------------------------+------------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+---------------------------+------------------------------+----------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25852/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-17 18:36 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 18:36 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-18 17:38 dpdklab
2023-08-18 17:09 dpdklab
2023-08-18 16:39 dpdklab
2023-08-18 15:58 dpdklab
2023-08-18 15:29 dpdklab
2023-08-18 2:52 dpdklab
2023-08-17 19:47 dpdklab
2023-08-17 19:11 dpdklab
2023-08-17 18:56 dpdklab
2023-08-17 18:55 dpdklab
2023-08-17 18:53 dpdklab
2023-08-17 18:52 dpdklab
2023-08-17 18:50 dpdklab
2023-08-17 18:49 dpdklab
2023-08-17 18:49 dpdklab
2023-08-17 18:49 dpdklab
2023-08-17 18:47 dpdklab
2023-08-17 18:45 dpdklab
2023-08-17 18:44 dpdklab
2023-08-17 18:44 dpdklab
2023-08-17 18:43 dpdklab
2023-08-17 18:43 dpdklab
2023-08-17 18:39 dpdklab
2023-08-17 18:39 dpdklab
2023-08-17 18:36 dpdklab
2023-08-17 18:34 dpdklab
2023-08-17 18:34 dpdklab
2023-08-17 18:33 dpdklab
2023-08-17 18:32 dpdklab
2023-08-17 18:32 dpdklab
2023-08-17 18:31 dpdklab
2023-08-17 18:31 dpdklab
2023-08-17 18:30 dpdklab
2023-08-17 18:30 dpdklab
2023-08-17 18:30 dpdklab
2023-08-17 18:30 dpdklab
2023-08-17 18:30 dpdklab
2023-08-17 18:30 dpdklab
2023-08-17 18:30 dpdklab
2023-08-17 18:30 dpdklab
2023-08-17 18:30 dpdklab
2023-08-17 18:30 dpdklab
2023-08-17 18:29 dpdklab
2023-08-17 18:29 dpdklab
2023-08-17 18:29 dpdklab
2023-08-17 18:29 dpdklab
2023-08-17 18:29 dpdklab
2023-08-17 18:28 dpdklab
2023-08-17 18:27 dpdklab
2023-08-17 18:27 dpdklab
2023-08-17 18:26 dpdklab
2023-08-17 18:26 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=64de68bf.170a0220.b9604.781cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.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).