From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135879 [PATCH] [v2,1/1] ethdev: parsing multiple represe
Date: Mon, 15 Jan 2024 09:09:52 -0800 (PST) [thread overview]
Message-ID: <65a566e0.920a0220.75c8b.b2abSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135879
_Testing PASS_
Submitter: Harman Kalra <hkalra@marvell.com>
Date: Monday, January 15 2024 15:57:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39a8b1251b204d3898b4c462184f60bda1b64698
135879 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28867/
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-15 17:09 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 17:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-16 18:19 dpdklab
2024-01-15 19:15 dpdklab
2024-01-15 17:39 dpdklab
2024-01-15 17:34 dpdklab
2024-01-15 17:30 dpdklab
2024-01-15 17:29 dpdklab
2024-01-15 17:29 dpdklab
2024-01-15 17:25 dpdklab
2024-01-15 17:25 dpdklab
2024-01-15 17:24 dpdklab
2024-01-15 17:23 dpdklab
2024-01-15 17:22 dpdklab
2024-01-15 17:18 dpdklab
2024-01-15 17:15 dpdklab
2024-01-15 17:15 dpdklab
2024-01-15 17:14 dpdklab
2024-01-15 17:12 dpdklab
2024-01-15 17:08 dpdklab
2024-01-15 17:06 dpdklab
2024-01-15 17:05 dpdklab
2024-01-15 17:04 dpdklab
2024-01-15 17:03 dpdklab
2024-01-15 17:01 dpdklab
2024-01-15 17:01 dpdklab
2024-01-15 16:58 dpdklab
2024-01-15 16:58 dpdklab
2024-01-15 16:57 dpdklab
2024-01-15 16:57 dpdklab
2024-01-15 16:55 dpdklab
2024-01-15 16:55 dpdklab
2024-01-15 16:54 dpdklab
2024-01-15 16:54 dpdklab
2024-01-15 16:53 dpdklab
2024-01-15 16:52 dpdklab
2024-01-15 16:52 dpdklab
2024-01-15 16:51 dpdklab
2024-01-15 16:51 dpdklab
2024-01-15 16:50 dpdklab
2024-01-15 16:48 dpdklab
2024-01-15 16:46 dpdklab
2024-01-15 16:45 dpdklab
2024-01-15 16:45 dpdklab
2024-01-15 16:45 dpdklab
2024-01-15 16:45 dpdklab
2024-01-15 16:44 dpdklab
2024-01-15 16:43 dpdklab
2024-01-15 16:43 dpdklab
2024-01-15 16:42 dpdklab
2024-01-15 16:41 dpdklab
2024-01-15 16:41 dpdklab
2024-01-15 16:41 dpdklab
2024-01-15 16:40 dpdklab
2024-01-15 16:40 dpdklab
2024-01-15 16:40 dpdklab
2024-01-15 16:38 dpdklab
2024-01-15 16:36 dpdklab
2024-01-15 16:35 dpdklab
2024-01-15 16:35 dpdklab
2024-01-15 16:34 dpdklab
2024-01-15 16:34 dpdklab
2024-01-15 16:34 dpdklab
2024-01-15 16:33 dpdklab
2024-01-15 16:32 dpdklab
2024-01-15 16:32 dpdklab
2024-01-15 16:32 dpdklab
2024-01-15 16:32 dpdklab
2024-01-15 16:32 dpdklab
2024-01-15 16:31 dpdklab
2024-01-15 16:31 dpdklab
2024-01-15 16:30 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=65a566e0.920a0220.75c8b.b2abSMTPIN_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).