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] 29c516fa4f5bac381825667b5bdb1ced4548c6bc
Date: Mon, 04 Mar 2024 23:45:53 -0800 (PST) [thread overview]
Message-ID: <65e6cdb1.170a0220.a7b81.c5baSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
29c516fa4f5bac381825667b5bdb1ced4548c6bc --> testing pass
Test environment and result as below:
+--------------------------+----------------+------------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_snow3g_autotest |
+==========================+================+==============================+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| Debian 12 (arm) | PASS | PASS |
+--------------------------+----------------+------------------------------+
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28308/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-05 7:45 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 7:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-08 19:46 dpdklab
2024-03-08 19:14 dpdklab
2024-03-08 18:52 dpdklab
2024-03-05 10:32 dpdklab
2024-03-05 8:16 dpdklab
2024-03-05 8:11 dpdklab
2024-03-05 8:09 dpdklab
2024-03-05 8:08 dpdklab
2024-03-05 8:07 dpdklab
2024-03-05 8:06 dpdklab
2024-03-05 8:06 dpdklab
2024-03-05 8:06 dpdklab
2024-03-05 8:06 dpdklab
2024-03-05 8:00 dpdklab
2024-03-05 7:58 dpdklab
2024-03-05 7:55 dpdklab
2024-03-05 7:55 dpdklab
2024-03-05 7:55 dpdklab
2024-03-05 7:55 dpdklab
2024-03-05 7:55 dpdklab
2024-03-05 7:55 dpdklab
2024-03-05 7:54 dpdklab
2024-03-05 7:54 dpdklab
2024-03-05 7:49 dpdklab
2024-03-05 7:48 dpdklab
2024-03-05 7:48 dpdklab
2024-03-05 7:46 dpdklab
2024-03-05 7:46 dpdklab
2024-03-05 7:46 dpdklab
2024-03-05 7:46 dpdklab
2024-03-05 7:45 dpdklab
2024-03-05 7:45 dpdklab
2024-03-05 7:45 dpdklab
2024-03-05 7:45 dpdklab
2024-03-05 7:44 dpdklab
2024-03-05 7:44 dpdklab
2024-03-05 7:44 dpdklab
2024-03-05 7:44 dpdklab
2024-03-05 7:44 dpdklab
2024-03-05 7:43 dpdklab
2024-03-05 7:43 dpdklab
2024-03-05 7:43 dpdklab
2024-03-05 7:43 dpdklab
2024-03-05 7:42 dpdklab
2024-03-05 7:42 dpdklab
2024-03-05 7:42 dpdklab
2024-03-05 7:42 dpdklab
2024-03-05 7:42 dpdklab
2024-03-05 7:42 dpdklab
2024-03-05 7:41 dpdklab
2024-03-05 7:41 dpdklab
2024-03-05 7:41 dpdklab
2024-03-05 7:41 dpdklab
2024-03-05 7:41 dpdklab
2024-03-05 7:40 dpdklab
2024-03-05 7:39 dpdklab
2024-03-05 7:39 dpdklab
2024-03-05 7:39 dpdklab
2024-03-05 7:39 dpdklab
2024-03-05 7:38 dpdklab
2024-03-05 7:38 dpdklab
2024-03-05 7:38 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=65e6cdb1.170a0220.a7b81.c5baSMTPIN_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).