From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136799 [PATCH] [v8] ethdev: add template table resize AP
Date: Wed, 14 Feb 2024 23:16:19 -0800 (PST) [thread overview]
Message-ID: <65cdba43.170a0220.f9506.9967SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136799
_Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thursday, February 15 2024 06:13:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:dccd6b7c68116a1cc044856aa35928e044640a8d
136799 --> 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 |
+--------------------------+------------------------------+---------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+---------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+---------------------------+----------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Debian 11 (Buster) (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/29155/
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-15 7:16 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 7:16 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 10:14 dpdklab
2024-02-15 10:04 dpdklab
2024-02-15 9:51 dpdklab
2024-02-15 9:30 dpdklab
2024-02-15 9:23 dpdklab
2024-02-15 9:05 dpdklab
2024-02-15 8:28 dpdklab
2024-02-15 8:21 dpdklab
2024-02-15 8:15 dpdklab
2024-02-15 8:15 dpdklab
2024-02-15 8:15 dpdklab
2024-02-15 8:13 dpdklab
2024-02-15 8:12 dpdklab
2024-02-15 8:12 dpdklab
2024-02-15 8:11 dpdklab
2024-02-15 8:03 dpdklab
2024-02-15 8:02 dpdklab
2024-02-15 8:01 dpdklab
2024-02-15 8:00 dpdklab
2024-02-15 7:59 dpdklab
2024-02-15 7:59 dpdklab
2024-02-15 7:58 dpdklab
2024-02-15 7:56 dpdklab
2024-02-15 7:56 dpdklab
2024-02-15 7:56 dpdklab
2024-02-15 7:56 dpdklab
2024-02-15 7:48 dpdklab
2024-02-15 7:47 dpdklab
2024-02-15 7:46 dpdklab
2024-02-15 7:46 dpdklab
2024-02-15 7:45 dpdklab
2024-02-15 7:45 dpdklab
2024-02-15 7:45 dpdklab
2024-02-15 7:44 dpdklab
2024-02-15 7:44 dpdklab
2024-02-15 7:43 dpdklab
2024-02-15 7:43 dpdklab
2024-02-15 7:41 dpdklab
2024-02-15 7:41 dpdklab
2024-02-15 7:35 dpdklab
2024-02-15 7:34 dpdklab
2024-02-15 7:34 dpdklab
2024-02-15 7:34 dpdklab
2024-02-15 7:33 dpdklab
2024-02-15 7:32 dpdklab
2024-02-15 7:22 dpdklab
2024-02-15 7:22 dpdklab
2024-02-15 7:21 dpdklab
2024-02-15 7:20 dpdklab
2024-02-15 7:20 dpdklab
2024-02-15 7:19 dpdklab
2024-02-15 7:19 dpdklab
2024-02-15 7:19 dpdklab
2024-02-15 7:18 dpdklab
2024-02-15 7:18 dpdklab
2024-02-15 7:18 dpdklab
2024-02-15 7:13 dpdklab
2024-02-15 7:13 dpdklab
2024-02-15 7:12 dpdklab
2024-02-15 7:12 dpdklab
2024-02-15 7:12 dpdklab
2024-02-15 7:11 dpdklab
2024-02-15 7:03 dpdklab
2024-02-15 7:02 dpdklab
2024-02-15 7:01 dpdklab
2024-02-15 6:57 dpdklab
2024-02-15 6:56 dpdklab
2024-02-15 6: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=65cdba43.170a0220.f9506.9967SMTPIN_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).