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] 238f67ca9cc00be4248b14d9ca4412edb7da62f6
Date: Wed, 19 Jul 2023 11:57:17 -0700 (PDT) [thread overview]
Message-ID: <64b8320d.0d0a0220.2114d.47a8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
238f67ca9cc00be4248b14d9ca4412edb7da62f6 --> testing pass
Test environment and result as below:
+-----------------------------+---------------------------+------------------------------+----------------+--------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test | lpm_autotest |
+=============================+===========================+==============================+================+==============+
| Debian 11 | PASS | PASS | SKIPPED | SKIPPED |
+-----------------------------+---------------------------+------------------------------+----------------+--------------+
| (32-bit) ARM Ubuntu 20.04.4 | SKIPPED | SKIPPED | PASS | SKIPPED |
+-----------------------------+---------------------------+------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | SKIPPED | PASS |
+-----------------------------+---------------------------+------------------------------+----------------+--------------+
Debian 11
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
(32-bit) ARM Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25538/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-19 18:57 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 18:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-19 21:49 dpdklab
2023-07-19 21:44 dpdklab
2023-07-19 21:39 dpdklab
2023-07-19 21:10 dpdklab
2023-07-19 21:06 dpdklab
2023-07-19 21:01 dpdklab
2023-07-19 19:44 dpdklab
2023-07-19 19:39 dpdklab
2023-07-19 19:38 dpdklab
2023-07-19 18:48 dpdklab
2023-07-19 18:36 dpdklab
2023-07-19 18:35 dpdklab
2023-07-19 18:33 dpdklab
2023-07-19 18:31 dpdklab
2023-07-19 18:29 dpdklab
2023-07-19 18:29 dpdklab
2023-07-19 18:28 dpdklab
2023-07-19 3:40 dpdklab
2023-07-19 2:16 dpdklab
2023-07-19 2:16 dpdklab
2023-07-19 2:08 dpdklab
2023-07-19 2:07 dpdklab
2023-07-19 2:05 dpdklab
2023-07-19 1:56 dpdklab
2023-07-19 1:39 dpdklab
2023-07-19 1:39 dpdklab
2023-07-19 1:38 dpdklab
2023-07-19 1:33 dpdklab
2023-07-19 1:29 dpdklab
2023-07-19 1:24 dpdklab
2023-07-19 1:23 dpdklab
2023-07-19 1:21 dpdklab
2023-07-19 1:19 dpdklab
2023-07-19 1:19 dpdklab
2023-07-19 1:12 dpdklab
2023-07-19 1:07 dpdklab
2023-07-19 1:05 dpdklab
2023-07-19 1:05 dpdklab
2023-07-19 1:05 dpdklab
2023-07-19 1:03 dpdklab
2023-07-19 1:01 dpdklab
2023-07-19 0:59 dpdklab
2023-07-19 0:58 dpdklab
2023-07-19 0:58 dpdklab
2023-07-19 0:58 dpdklab
2023-07-19 0:58 dpdklab
2023-07-19 0:57 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=64b8320d.0d0a0220.2114d.47a8SMTPIN_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).