From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135646-135647 [PATCH] [v7,2/2] doc: add document for ice
Date: Tue, 02 Jan 2024 03:52:50 -0800 (PST) [thread overview]
Message-ID: <6593f912.050a0220.2856f.ff57SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135647
_Testing PASS_
Submitter: Qi Zhang <qi.z.zhang@intel.com>
Date: Tuesday, January 02 2024 12:39:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135646-135647 --> testing pass
Test environment and result as below:
+-----------------------+------------------------------+---------------------------+----------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+=======================+==============================+===========================+================+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+-----------------------+------------------------------+---------------------------+----------------+
| CentOS Stream 9 (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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28762/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-02 11:52 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 11:52 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-02 13:18 dpdklab
2024-01-02 12:46 dpdklab
2024-01-02 12:42 dpdklab
2024-01-02 12:40 dpdklab
2024-01-02 12:33 dpdklab
2024-01-02 12:32 dpdklab
2024-01-02 12:31 dpdklab
2024-01-02 12:31 dpdklab
2024-01-02 12:31 dpdklab
2024-01-02 12:29 dpdklab
2024-01-02 12:29 dpdklab
2024-01-02 12:28 dpdklab
2024-01-02 12:28 dpdklab
2024-01-02 12:28 dpdklab
2024-01-02 12:28 dpdklab
2024-01-02 12:27 dpdklab
2024-01-02 12:27 dpdklab
2024-01-02 12:26 dpdklab
2024-01-02 12:24 dpdklab
2024-01-02 12:23 dpdklab
2024-01-02 12:23 dpdklab
2024-01-02 12:22 dpdklab
2024-01-02 12:22 dpdklab
2024-01-02 12:22 dpdklab
2024-01-02 12:21 dpdklab
2024-01-02 12:21 dpdklab
2024-01-02 12:21 dpdklab
2024-01-02 12:06 dpdklab
2024-01-02 12:06 dpdklab
2024-01-02 12:05 dpdklab
2024-01-02 12:05 dpdklab
2024-01-02 12:05 dpdklab
2024-01-02 12:05 dpdklab
2024-01-02 12:05 dpdklab
2024-01-02 12:04 dpdklab
2024-01-02 12:04 dpdklab
2024-01-02 12:04 dpdklab
2024-01-02 12:02 dpdklab
2024-01-02 12:02 dpdklab
2024-01-02 12:02 dpdklab
2024-01-02 12:01 dpdklab
2024-01-02 12:01 dpdklab
2024-01-02 12:01 dpdklab
2024-01-02 12:01 dpdklab
2024-01-02 12:00 dpdklab
2024-01-02 11:56 dpdklab
2024-01-02 11:55 dpdklab
2024-01-02 11:54 dpdklab
2024-01-02 11:54 dpdklab
2024-01-02 11:53 dpdklab
2024-01-02 11:53 dpdklab
2024-01-02 11:53 dpdklab
2024-01-02 11:53 dpdklab
2024-01-02 11:52 dpdklab
2024-01-02 11:52 dpdklab
2024-01-02 11:52 dpdklab
2024-01-02 11:51 dpdklab
2024-01-02 11:51 dpdklab
2024-01-02 11:50 dpdklab
2024-01-02 11:50 dpdklab
2024-01-02 11:49 dpdklab
2024-01-02 11:48 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=6593f912.050a0220.2856f.ff57SMTPIN_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).