From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133571 [PATCH] [v3] net/mlx5: add indirect encap decap s
Date: Sun, 29 Oct 2023 06:36:32 -0700 (PDT) [thread overview]
Message-ID: <653e5fe0.0c0a0220.e3103.7179SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133571
_Testing PASS_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Sunday, October 29 2023 12:53:48
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: master
CommitID:c5195f9df1508e5aff4b877a1a6ccb50085f4f72
133571 --> 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 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+---------------------------+----------------+
| Fedora 37 (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
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28131/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-29 13:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 13:36 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-29 14:46 dpdklab
2023-10-29 14:13 dpdklab
2023-10-29 14:02 dpdklab
2023-10-29 13:57 dpdklab
2023-10-29 13:56 dpdklab
2023-10-29 13:54 dpdklab
2023-10-29 13:52 dpdklab
2023-10-29 13:50 dpdklab
2023-10-29 13:48 dpdklab
2023-10-29 13:46 dpdklab
2023-10-29 13:45 dpdklab
2023-10-29 13:45 dpdklab
2023-10-29 13:44 dpdklab
2023-10-29 13:43 dpdklab
2023-10-29 13:42 dpdklab
2023-10-29 13:41 dpdklab
2023-10-29 13:39 dpdklab
2023-10-29 13:39 dpdklab
2023-10-29 13:39 dpdklab
2023-10-29 13:39 dpdklab
2023-10-29 13:39 dpdklab
2023-10-29 13:38 dpdklab
2023-10-29 13:38 dpdklab
2023-10-29 13:38 dpdklab
2023-10-29 13:38 dpdklab
2023-10-29 13:37 dpdklab
2023-10-29 13:37 dpdklab
2023-10-29 13:37 dpdklab
2023-10-29 13:37 dpdklab
2023-10-29 13:36 dpdklab
2023-10-29 13:36 dpdklab
2023-10-29 13:36 dpdklab
2023-10-29 13:35 dpdklab
2023-10-29 13:35 dpdklab
2023-10-29 13:35 dpdklab
2023-10-29 13:35 dpdklab
2023-10-29 13:34 dpdklab
2023-10-29 13:34 dpdklab
2023-10-29 13:34 dpdklab
2023-10-29 13:33 dpdklab
2023-10-29 13:31 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=653e5fe0.0c0a0220.e3103.7179SMTPIN_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).