From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Sunil Kumar Kori <skori@marvell.com>
Subject: |SUCCESS| pw135074 [PATCH] [v2,1/1] app/graph: generate cmdline boil
Date: Tue, 12 Dec 2023 19:56:50 -0800 (PST) [thread overview]
Message-ID: <65792b82.0d0a0220.36083.db15SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135074
_Testing PASS_
Submitter: Sunil Kumar Kori <skori@marvell.com>
Date: Tuesday, December 12 2023 17:05:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
135074 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28602/
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-13 3:56 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 3:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-13 6:50 dpdklab
2023-12-13 5:07 dpdklab
2023-12-13 5:00 dpdklab
2023-12-13 4:52 dpdklab
2023-12-13 4:44 dpdklab
2023-12-13 4:40 dpdklab
2023-12-13 4:39 dpdklab
2023-12-13 4:31 dpdklab
2023-12-13 4:28 dpdklab
2023-12-13 4:25 dpdklab
2023-12-13 4:25 dpdklab
2023-12-13 4:24 dpdklab
2023-12-13 4:24 dpdklab
2023-12-13 4:19 dpdklab
2023-12-13 4:17 dpdklab
2023-12-13 4:17 dpdklab
2023-12-13 4:17 dpdklab
2023-12-13 4:14 dpdklab
2023-12-13 4:08 dpdklab
2023-12-13 4:08 dpdklab
2023-12-13 4:07 dpdklab
2023-12-13 4:06 dpdklab
2023-12-13 4:06 dpdklab
2023-12-13 4:05 dpdklab
2023-12-13 4:05 dpdklab
2023-12-13 4:03 dpdklab
2023-12-13 4:01 dpdklab
2023-12-13 4:00 dpdklab
2023-12-13 3:59 dpdklab
2023-12-13 3:59 dpdklab
2023-12-13 3:59 dpdklab
2023-12-13 3:58 dpdklab
2023-12-13 3:58 dpdklab
2023-12-13 3:57 dpdklab
2023-12-13 3:57 dpdklab
2023-12-13 3:56 dpdklab
2023-12-13 3:56 dpdklab
2023-12-13 3:55 dpdklab
2023-12-13 3:54 dpdklab
2023-12-13 3:53 dpdklab
2023-12-13 3:52 dpdklab
2023-12-13 3:52 dpdklab
2023-12-13 3:51 dpdklab
2023-12-13 3:50 dpdklab
2023-12-13 3:47 dpdklab
2023-12-13 3:47 dpdklab
2023-12-13 3:46 dpdklab
2023-12-13 3:46 dpdklab
2023-12-13 3:42 dpdklab
2023-12-13 3:34 dpdklab
2023-12-13 3:34 dpdklab
2023-12-13 3:33 dpdklab
2023-12-13 3:31 dpdklab
2023-12-13 3:31 dpdklab
2023-12-13 3:29 dpdklab
2023-12-13 3:29 dpdklab
2023-12-13 3:26 dpdklab
2023-12-13 3:21 dpdklab
2023-12-13 3:18 dpdklab
2023-12-13 3:09 dpdklab
2023-12-13 3:08 dpdklab
2023-12-13 3:08 dpdklab
2023-12-13 3:02 dpdklab
2023-12-13 2:57 dpdklab
2023-12-13 2:55 dpdklab
2023-12-13 2:53 dpdklab
2023-12-13 2:53 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=65792b82.0d0a0220.36083.db15SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=skori@marvell.com \
--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).