From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134878 [PATCH] buildtools/dpdk-cmdline-gen: fix code gen
Date: Tue, 05 Dec 2023 06:51:24 -0800 (PST) [thread overview]
Message-ID: <656f38ec.620a0220.240f9.931eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134878
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, December 05 2023 11:31:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a526461b0764de52b09b073df84f9e87ec120c93
134878 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| Windows Server 2022 | PASS |
+---------------------+--------------------+
| CentOS Stream 9 | PASS |
+---------------------+--------------------+
| FreeBSD 13 | PASS |
+---------------------+--------------------+
| Debian Bullseye | PASS |
+---------------------+--------------------+
| RHEL8 | PASS |
+---------------------+--------------------+
| Fedora 37 | PASS |
+---------------------+--------------------+
| Fedora 38 | PASS |
+---------------------+--------------------+
| Ubuntu 20.04 | PASS |
+---------------------+--------------------+
| Ubuntu 22.04 | PASS |
+---------------------+--------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28532/
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-05 14:51 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 14:51 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-05 17:33 dpdklab
2023-12-05 17:24 dpdklab
2023-12-05 15:46 dpdklab
2023-12-05 15:16 dpdklab
2023-12-05 15:09 dpdklab
2023-12-05 15:07 dpdklab
2023-12-05 15:07 dpdklab
2023-12-05 15:07 dpdklab
2023-12-05 15:06 dpdklab
2023-12-05 15:04 dpdklab
2023-12-05 15:04 dpdklab
2023-12-05 15:04 dpdklab
2023-12-05 15:02 dpdklab
2023-12-05 15:02 dpdklab
2023-12-05 15:01 dpdklab
2023-12-05 15:01 dpdklab
2023-12-05 14:59 dpdklab
2023-12-05 14:55 dpdklab
2023-12-05 14:55 dpdklab
2023-12-05 14:55 dpdklab
2023-12-05 14:54 dpdklab
2023-12-05 14:54 dpdklab
2023-12-05 14:53 dpdklab
2023-12-05 14:53 dpdklab
2023-12-05 14:53 dpdklab
2023-12-05 14:53 dpdklab
2023-12-05 14:53 dpdklab
2023-12-05 14:53 dpdklab
2023-12-05 14:52 dpdklab
2023-12-05 14:52 dpdklab
2023-12-05 14:51 dpdklab
2023-12-05 14:49 dpdklab
2023-12-05 14:49 dpdklab
2023-12-05 14:49 dpdklab
2023-12-05 14:47 dpdklab
2023-12-05 14:47 dpdklab
2023-12-05 14:46 dpdklab
2023-12-05 14:46 dpdklab
2023-12-05 14:43 dpdklab
2023-12-05 14:43 dpdklab
2023-12-05 14:27 dpdklab
2023-12-05 14:27 dpdklab
2023-12-05 14:26 dpdklab
2023-12-05 14:17 dpdklab
2023-12-05 14:17 dpdklab
2023-12-05 14:05 dpdklab
2023-12-05 14:05 dpdklab
2023-12-05 14:03 dpdklab
2023-12-05 14:03 dpdklab
2023-12-05 14:03 dpdklab
2023-12-05 13:45 dpdklab
2023-12-05 13:34 dpdklab
2023-12-05 13:33 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=656f38ec.620a0220.240f9.931eSMTPIN_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).