From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130181-130185 [PATCH] [v2,6/6] devtools: forbid new dire
Date: Fri, 11 Aug 2023 12:32:22 -0700 (PDT) [thread overview]
Message-ID: <64d68cc6.0c0a0220.127fa.bdaeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130185
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Friday, August 11 2023 17:32:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70b6941e4e22d67bc10495d1638234a7e974f582
130181-130185 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| FreeBSD 13 | PASS |
+---------------------+--------------------+
| Windows Server 2019 | PASS |
+---------------------+--------------------+
| Fedora 38 | PASS |
+---------------------+--------------------+
| Debian Buster | PASS |
+---------------------+--------------------+
| Debian Bullseye | PASS |
+---------------------+--------------------+
| CentOS Stream 9 | PASS |
+---------------------+--------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
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
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/27313/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-11 19:32 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 19:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-13 23:52 dpdklab
2023-08-13 23:43 dpdklab
2023-08-13 23:43 dpdklab
2023-08-13 23:40 dpdklab
2023-08-13 23:38 dpdklab
2023-08-13 23:36 dpdklab
2023-08-13 23:32 dpdklab
2023-08-13 23:28 dpdklab
2023-08-13 23:24 dpdklab
2023-08-13 23:23 dpdklab
2023-08-13 23:22 dpdklab
2023-08-13 23:21 dpdklab
2023-08-13 21:04 dpdklab
2023-08-13 19:06 dpdklab
2023-08-12 12:56 dpdklab
2023-08-12 12:52 dpdklab
2023-08-12 12:35 dpdklab
2023-08-12 12:29 dpdklab
2023-08-12 12:25 dpdklab
2023-08-12 11:39 dpdklab
2023-08-11 21:07 dpdklab
2023-08-11 20:39 dpdklab
2023-08-11 20:38 dpdklab
2023-08-11 20:33 dpdklab
2023-08-11 20:33 dpdklab
2023-08-11 20:31 dpdklab
2023-08-11 20:19 dpdklab
2023-08-11 20:17 dpdklab
2023-08-11 20:11 dpdklab
2023-08-11 20:10 dpdklab
2023-08-11 20:06 dpdklab
2023-08-11 20:05 dpdklab
2023-08-11 20:05 dpdklab
2023-08-11 20:04 dpdklab
2023-08-11 20:04 dpdklab
2023-08-11 20:04 dpdklab
2023-08-11 20:03 dpdklab
2023-08-11 20:03 dpdklab
2023-08-11 20:03 dpdklab
2023-08-11 20:03 dpdklab
2023-08-11 20:02 dpdklab
2023-08-11 20:01 dpdklab
2023-08-11 20:01 dpdklab
2023-08-11 20:01 dpdklab
2023-08-11 20:00 dpdklab
2023-08-11 19:59 dpdklab
2023-08-11 19:55 dpdklab
2023-08-11 19:42 dpdklab
2023-08-11 19:42 dpdklab
2023-08-11 19:42 dpdklab
2023-08-11 19:41 dpdklab
2023-08-11 19:41 dpdklab
2023-08-11 19:40 dpdklab
2023-08-11 19:39 dpdklab
2023-08-11 19:37 dpdklab
2023-08-11 19:36 dpdklab
2023-08-11 19:35 dpdklab
2023-08-11 19:35 dpdklab
2023-08-11 19:34 dpdklab
2023-08-11 19:34 dpdklab
2023-08-11 19:24 dpdklab
2023-08-11 19:24 dpdklab
2023-08-11 19:23 dpdklab
2023-08-11 19:18 dpdklab
2023-08-11 19:18 dpdklab
2023-08-11 19:17 dpdklab
2023-08-11 19:17 dpdklab
2023-08-11 19:15 dpdklab
2023-08-11 19:15 dpdklab
2023-08-11 19:13 dpdklab
2023-08-11 19:13 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=64d68cc6.0c0a0220.127fa.bdaeSMTPIN_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).