From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137009-137013 [PATCH] [v2,5/5] net/cnxk: select optimize
Date: Thu, 22 Feb 2024 03:54:59 -0800 (PST) [thread overview]
Message-ID: <65d73613.050a0220.7182f.7dc2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137013
_Testing PASS_
Submitter: Rahul Bhansali <rbhansali@marvell.com>
Date: Thursday, February 22 2024 10:07:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137009-137013 --> testing pass
Test environment and result as below:
+--------------------------+------------------------------+--------------+---------------------------+----------------+
| Environment | cryptodev_sw_snow3g_autotest | lpm_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+==========================+==============================+==============+===========================+================+
| Debian 11 (arm) | PASS | SKIPPED | PASS | SKIPPED |
+--------------------------+------------------------------+--------------+---------------------------+----------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | PASS | SKIPPED | SKIPPED |
+--------------------------+------------------------------+--------------+---------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+--------------+---------------------------+----------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
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 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29221/
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-22 11:55 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 11:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 23:24 dpdklab
2024-02-23 4:05 dpdklab
2024-02-23 3:58 dpdklab
2024-02-22 12:45 dpdklab
2024-02-22 12:30 dpdklab
2024-02-22 12:26 dpdklab
2024-02-22 12:25 dpdklab
2024-02-22 12:23 dpdklab
2024-02-22 12:22 dpdklab
2024-02-22 12:21 dpdklab
2024-02-22 12:21 dpdklab
2024-02-22 12:20 dpdklab
2024-02-22 12:09 dpdklab
2024-02-22 12:05 dpdklab
2024-02-22 12:04 dpdklab
2024-02-22 11:48 dpdklab
2024-02-22 11:38 dpdklab
2024-02-22 11:38 dpdklab
2024-02-22 11:37 dpdklab
2024-02-22 11:36 dpdklab
2024-02-22 11:36 dpdklab
2024-02-22 11:36 dpdklab
2024-02-22 11:35 dpdklab
2024-02-22 11:34 dpdklab
2024-02-22 11:33 dpdklab
2024-02-22 11:33 dpdklab
2024-02-22 11:33 dpdklab
2024-02-22 11:33 dpdklab
2024-02-22 11:30 dpdklab
2024-02-22 11:18 dpdklab
2024-02-22 11:17 dpdklab
2024-02-22 11:17 dpdklab
2024-02-22 11:17 dpdklab
2024-02-22 11:12 dpdklab
2024-02-22 11:11 dpdklab
2024-02-22 11:11 dpdklab
2024-02-22 11:11 dpdklab
2024-02-22 11:11 dpdklab
2024-02-22 11:10 dpdklab
2024-02-22 11:09 dpdklab
2024-02-22 11:01 dpdklab
2024-02-22 11:00 dpdklab
2024-02-22 11:00 dpdklab
2024-02-22 11:00 dpdklab
2024-02-22 10:56 dpdklab
2024-02-22 10:56 dpdklab
2024-02-22 10:54 dpdklab
2024-02-22 10:53 dpdklab
2024-02-22 10:53 dpdklab
2024-02-22 10:53 dpdklab
2024-02-22 10:52 dpdklab
2024-02-22 10:52 dpdklab
2024-02-22 10:50 dpdklab
2024-02-22 10:48 dpdklab
2024-02-22 10:48 dpdklab
2024-02-22 10:47 dpdklab
2024-02-22 10:47 dpdklab
2024-02-22 10:45 dpdklab
2024-02-22 10:45 dpdklab
2024-02-22 10:44 dpdklab
2024-02-22 10:42 dpdklab
2024-02-22 10:42 dpdklab
2024-02-22 10:42 dpdklab
2024-02-22 10:42 dpdklab
2024-02-22 10:41 dpdklab
2024-02-22 10:41 dpdklab
2024-02-22 10:41 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=65d73613.050a0220.7182f.7dc2SMTPIN_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).