From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134886 [PATCH] cfgfile: increase value length
Date: Wed, 06 Dec 2023 04:46:27 -0800 (PST) [thread overview]
Message-ID: <65706d23.050a0220.3c595.9a5aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134886
_Testing PASS_
Submitter: Vipin Varghese <vipin.varghese@amd.com>
Date: Wednesday, December 06 2023 11:29:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a526461b0764de52b09b073df84f9e87ec120c93
134886 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28538/
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-06 12:46 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 12:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-06 16:02 dpdklab
2023-12-06 15:44 dpdklab
2023-12-06 15:42 dpdklab
2023-12-06 15:21 dpdklab
2023-12-06 15:04 dpdklab
2023-12-06 13:54 dpdklab
2023-12-06 13:44 dpdklab
2023-12-06 13:29 dpdklab
2023-12-06 13:05 dpdklab
2023-12-06 13:05 dpdklab
2023-12-06 13:02 dpdklab
2023-12-06 12:56 dpdklab
2023-12-06 12:54 dpdklab
2023-12-06 12:54 dpdklab
2023-12-06 12:52 dpdklab
2023-12-06 12:52 dpdklab
2023-12-06 12:50 dpdklab
2023-12-06 12:48 dpdklab
2023-12-06 12:42 dpdklab
2023-12-06 12:41 dpdklab
2023-12-06 12:38 dpdklab
2023-12-06 12:36 dpdklab
2023-12-06 12:35 dpdklab
2023-12-06 12:32 dpdklab
2023-12-06 12:31 dpdklab
2023-12-06 12:30 dpdklab
2023-12-06 12:30 dpdklab
2023-12-06 12:29 dpdklab
2023-12-06 12:29 dpdklab
2023-12-06 12:28 dpdklab
2023-12-06 12:28 dpdklab
2023-12-06 12:28 dpdklab
2023-12-06 12:27 dpdklab
2023-12-06 12:27 dpdklab
2023-12-06 12:25 dpdklab
2023-12-06 12:23 dpdklab
2023-12-06 12:22 dpdklab
2023-12-06 12:21 dpdklab
2023-12-06 12:20 dpdklab
2023-12-06 12:18 dpdklab
2023-12-06 12:18 dpdklab
2023-12-06 12:17 dpdklab
2023-12-06 12:17 dpdklab
2023-12-06 12:16 dpdklab
2023-12-06 12:16 dpdklab
2023-12-06 12:15 dpdklab
2023-12-06 12:14 dpdklab
2023-12-06 12:13 dpdklab
2023-12-06 12:13 dpdklab
2023-12-06 12:13 dpdklab
2023-12-06 12:09 dpdklab
2023-12-06 12:07 dpdklab
2023-12-06 12:05 dpdklab
2023-12-06 12:02 dpdklab
2023-12-06 12:02 dpdklab
2023-12-06 12:02 dpdklab
[not found] <20231206112952.1588-1-vipin.varghese@amd.com>
2023-12-06 11:11 ` qemudev
2023-12-06 11:16 ` qemudev
2023-12-06 11:32 ` checkpatch
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=65706d23.050a0220.3c595.9a5aSMTPIN_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).