From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134927-134928 [PATCH] [v2,2/2] net/cnxk: dump Rx descrip
Date: Thu, 07 Dec 2023 10:49:14 -0800 (PST) [thread overview]
Message-ID: <657213aa.170a0220.17376.0735SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134928
_Testing PASS_
Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Thursday, December 07 2023 13:46:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
134927-134928 --> testing pass
Test environment and result as below:
+--------------------------+----------------+
| Environment | dpdk_unit_test |
+==========================+================+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------+----------------+
| Fedora 37 (ARM) | PASS |
+--------------------------+----------------+
| Fedora 38 (ARM) | PASS |
+--------------------------+----------------+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------+----------------+
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
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.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/28553/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-07 18:49 UTC|newest]
Thread overview: 159+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 18:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-08 17:10 dpdklab
2023-12-08 3:44 dpdklab
2023-12-08 2:29 dpdklab
2023-12-08 2:16 dpdklab
2023-12-08 2:12 dpdklab
2023-12-08 2:12 dpdklab
2023-12-08 2:04 dpdklab
2023-12-08 1:40 dpdklab
2023-12-08 1:40 dpdklab
2023-12-08 1:37 dpdklab
2023-12-08 1:34 dpdklab
2023-12-08 1:33 dpdklab
2023-12-08 1:29 dpdklab
2023-12-08 1:29 dpdklab
2023-12-08 1:20 dpdklab
2023-12-08 1:14 dpdklab
2023-12-08 1:13 dpdklab
2023-12-08 1:12 dpdklab
2023-12-08 1:12 dpdklab
2023-12-08 1:12 dpdklab
2023-12-08 1:11 dpdklab
2023-12-08 1:11 dpdklab
2023-12-08 1:11 dpdklab
2023-12-08 1:10 dpdklab
2023-12-08 1:10 dpdklab
2023-12-08 1:10 dpdklab
2023-12-08 1:07 dpdklab
2023-12-08 1:05 dpdklab
2023-12-08 1:04 dpdklab
2023-12-08 1:04 dpdklab
2023-12-08 1:04 dpdklab
2023-12-08 1:02 dpdklab
2023-12-08 1:01 dpdklab
2023-12-08 1:01 dpdklab
2023-12-08 1:01 dpdklab
2023-12-08 1:00 dpdklab
2023-12-08 1:00 dpdklab
2023-12-08 1:00 dpdklab
2023-12-08 0:59 dpdklab
2023-12-08 0:59 dpdklab
2023-12-08 0:58 dpdklab
2023-12-08 0:58 dpdklab
2023-12-08 0:57 dpdklab
2023-12-08 0:57 dpdklab
2023-12-08 0:57 dpdklab
2023-12-08 0:56 dpdklab
2023-12-08 0:55 dpdklab
2023-12-08 0:26 dpdklab
2023-12-08 0:03 dpdklab
2023-12-07 23:59 dpdklab
2023-12-07 23:59 dpdklab
2023-12-07 23:58 dpdklab
2023-12-07 23:58 dpdklab
2023-12-07 23:37 dpdklab
2023-12-07 23:36 dpdklab
2023-12-07 23:28 dpdklab
2023-12-07 23:25 dpdklab
2023-12-07 23:25 dpdklab
2023-12-07 23:24 dpdklab
2023-12-07 23:23 dpdklab
2023-12-07 23:22 dpdklab
2023-12-07 23:21 dpdklab
2023-12-07 23:21 dpdklab
2023-12-07 23:21 dpdklab
2023-12-07 23:21 dpdklab
2023-12-07 23:21 dpdklab
2023-12-07 23:21 dpdklab
2023-12-07 23:20 dpdklab
2023-12-07 23:20 dpdklab
2023-12-07 23:20 dpdklab
2023-12-07 23:20 dpdklab
2023-12-07 23:20 dpdklab
2023-12-07 23:19 dpdklab
2023-12-07 23:19 dpdklab
2023-12-07 23:19 dpdklab
2023-12-07 23:19 dpdklab
2023-12-07 23:19 dpdklab
2023-12-07 23:19 dpdklab
2023-12-07 23:18 dpdklab
2023-12-07 23:18 dpdklab
2023-12-07 23:18 dpdklab
2023-12-07 23:18 dpdklab
2023-12-07 23:18 dpdklab
2023-12-07 23:18 dpdklab
2023-12-07 23:18 dpdklab
2023-12-07 23:17 dpdklab
2023-12-07 23:17 dpdklab
2023-12-07 23:17 dpdklab
2023-12-07 23:16 dpdklab
2023-12-07 23:11 dpdklab
2023-12-07 22:30 dpdklab
2023-12-07 22:30 dpdklab
2023-12-07 22:28 dpdklab
2023-12-07 22:28 dpdklab
2023-12-07 22:24 dpdklab
2023-12-07 20:46 dpdklab
2023-12-07 20:44 dpdklab
2023-12-07 20:42 dpdklab
2023-12-07 20:37 dpdklab
2023-12-07 19:40 dpdklab
2023-12-07 19:34 dpdklab
2023-12-07 19:18 dpdklab
2023-12-07 19:13 dpdklab
2023-12-07 18:54 dpdklab
2023-12-07 18:45 dpdklab
2023-12-07 18:42 dpdklab
2023-12-07 18:40 dpdklab
2023-12-07 18:26 dpdklab
2023-12-07 18:17 dpdklab
2023-12-07 18:17 dpdklab
2023-12-07 18:17 dpdklab
2023-12-07 18:16 dpdklab
2023-12-07 18:14 dpdklab
2023-12-07 18:13 dpdklab
2023-12-07 18:13 dpdklab
2023-12-07 18:12 dpdklab
2023-12-07 18:12 dpdklab
2023-12-07 18:12 dpdklab
2023-12-07 18:12 dpdklab
2023-12-07 18:12 dpdklab
2023-12-07 18:12 dpdklab
2023-12-07 18:11 dpdklab
2023-12-07 18:11 dpdklab
2023-12-07 18:10 dpdklab
2023-12-07 18:10 dpdklab
2023-12-07 18:10 dpdklab
2023-12-07 18:10 dpdklab
2023-12-07 18:10 dpdklab
2023-12-07 18:09 dpdklab
2023-12-07 18:09 dpdklab
2023-12-07 18:09 dpdklab
2023-12-07 18:09 dpdklab
2023-12-07 18:08 dpdklab
2023-12-07 18:07 dpdklab
2023-12-07 18:07 dpdklab
2023-12-07 18:07 dpdklab
2023-12-07 18:07 dpdklab
2023-12-07 18:06 dpdklab
2023-12-07 18:06 dpdklab
2023-12-07 18:06 dpdklab
2023-12-07 18:05 dpdklab
2023-12-07 18:05 dpdklab
2023-12-07 18:05 dpdklab
2023-12-07 18:04 dpdklab
2023-12-07 18:04 dpdklab
2023-12-07 18:04 dpdklab
2023-12-07 18:03 dpdklab
2023-12-07 18:03 dpdklab
2023-12-07 18:02 dpdklab
2023-12-07 18:02 dpdklab
2023-12-07 17:46 dpdklab
2023-12-07 17:46 dpdklab
2023-12-07 17:45 dpdklab
2023-12-07 17:45 dpdklab
2023-12-07 17:45 dpdklab
2023-12-07 17:45 dpdklab
2023-12-07 17:39 dpdklab
2023-12-07 17:35 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=657213aa.170a0220.17376.0735SMTPIN_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).