From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136388-136410 [PATCH] [v9,23/23] drivers: remove use of
Date: Mon, 05 Feb 2024 11:20:28 -0800 (PST) [thread overview]
Message-ID: <65c134fc.050a0220.98968.0f11SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136410
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, February 05 2024 17:43:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a4ce111cc89f580b8c4aad51bdb061acbdfde86b
136388-136410 --> testing pass
Test environment and result as below:
+-----------------------+--------------+---------------------------+------------------------------+----------------+
| Environment | lpm_autotest | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+=======================+==============+===========================+==============================+================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED | SKIPPED | SKIPPED |
+-----------------------+--------------+---------------------------+------------------------------+----------------+
| Debian 11 (arm) | SKIPPED | PASS | PASS | SKIPPED |
+-----------------------+--------------+---------------------------+------------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | SKIPPED | PASS |
+-----------------------+--------------+---------------------------+------------------------------+----------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29050/
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-05 19:20 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 19:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 20:40 dpdklab
2024-02-05 20:39 dpdklab
2024-02-05 20:36 dpdklab
2024-02-05 20:16 dpdklab
2024-02-05 19:57 dpdklab
2024-02-05 19:52 dpdklab
2024-02-05 19:51 dpdklab
2024-02-05 19:51 dpdklab
2024-02-05 19:43 dpdklab
2024-02-05 19:41 dpdklab
2024-02-05 19:40 dpdklab
2024-02-05 19:40 dpdklab
2024-02-05 19:37 dpdklab
2024-02-05 19:36 dpdklab
2024-02-05 19:34 dpdklab
2024-02-05 19:33 dpdklab
2024-02-05 19:32 dpdklab
2024-02-05 19:31 dpdklab
2024-02-05 19:30 dpdklab
2024-02-05 19:29 dpdklab
2024-02-05 19:28 dpdklab
2024-02-05 19:25 dpdklab
2024-02-05 19:23 dpdklab
2024-02-05 19:22 dpdklab
2024-02-05 19:22 dpdklab
2024-02-05 19:22 dpdklab
2024-02-05 19:21 dpdklab
2024-02-05 19:20 dpdklab
2024-02-05 19:20 dpdklab
2024-02-05 19:19 dpdklab
2024-02-05 19:19 dpdklab
2024-02-05 19:18 dpdklab
2024-02-05 19:18 dpdklab
2024-02-05 19:14 dpdklab
2024-02-05 19:13 dpdklab
2024-02-05 19:11 dpdklab
2024-02-05 19:11 dpdklab
2024-02-05 19:11 dpdklab
2024-02-05 19:10 dpdklab
2024-02-05 19:10 dpdklab
2024-02-05 19:10 dpdklab
2024-02-05 19:10 dpdklab
2024-02-05 19:10 dpdklab
2024-02-05 19:09 dpdklab
2024-02-05 19:09 dpdklab
2024-02-05 19:09 dpdklab
2024-02-05 19:09 dpdklab
2024-02-05 19:08 dpdklab
2024-02-05 19:08 dpdklab
2024-02-05 18:57 dpdklab
2024-02-05 18:56 dpdklab
2024-02-05 18:56 dpdklab
2024-02-05 18:56 dpdklab
2024-02-05 18:55 dpdklab
2024-02-05 18:55 dpdklab
2024-02-05 18:55 dpdklab
2024-02-05 18:54 dpdklab
2024-02-05 18:54 dpdklab
2024-02-05 18:54 dpdklab
2024-02-05 18:54 dpdklab
2024-02-05 18:54 dpdklab
2024-02-05 18:53 dpdklab
2024-02-05 18:53 dpdklab
2024-02-05 18:52 dpdklab
2024-02-05 18:52 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=65c134fc.050a0220.98968.0f11SMTPIN_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).