From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136602 [PATCH] [v2] eal: provide macro to allocate and n
Date: Mon, 12 Feb 2024 13:44:38 -0800 (PST) [thread overview]
Message-ID: <65ca9146.0d0a0220.3dee9.9b6cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136602
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Monday, February 12 2024 20:51:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39fbd379aa448fda098575f6052dfcdf1dc8e23b
136602 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29121/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-12 21:44 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 21:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-12 23:33 dpdklab
2024-02-12 23:30 dpdklab
2024-02-12 22:56 dpdklab
2024-02-12 22:41 dpdklab
2024-02-12 22:36 dpdklab
2024-02-12 22:35 dpdklab
2024-02-12 22:34 dpdklab
2024-02-12 22:33 dpdklab
2024-02-12 22:32 dpdklab
2024-02-12 22:32 dpdklab
2024-02-12 22:31 dpdklab
2024-02-12 22:30 dpdklab
2024-02-12 22:30 dpdklab
2024-02-12 22:30 dpdklab
2024-02-12 22:29 dpdklab
2024-02-12 22:26 dpdklab
2024-02-12 22:26 dpdklab
2024-02-12 22:21 dpdklab
2024-02-12 22:21 dpdklab
2024-02-12 22:19 dpdklab
2024-02-12 22:19 dpdklab
2024-02-12 22:18 dpdklab
2024-02-12 22:17 dpdklab
2024-02-12 22:14 dpdklab
2024-02-12 22:14 dpdklab
2024-02-12 22:14 dpdklab
2024-02-12 22:13 dpdklab
2024-02-12 22:13 dpdklab
2024-02-12 22:11 dpdklab
2024-02-12 22:11 dpdklab
2024-02-12 22:11 dpdklab
2024-02-12 22:09 dpdklab
2024-02-12 22:09 dpdklab
2024-02-12 22:08 dpdklab
2024-02-12 22:07 dpdklab
2024-02-12 22:03 dpdklab
2024-02-12 22:03 dpdklab
2024-02-12 22:02 dpdklab
2024-02-12 22:01 dpdklab
2024-02-12 21:58 dpdklab
2024-02-12 21:54 dpdklab
2024-02-12 21:53 dpdklab
2024-02-12 21:53 dpdklab
2024-02-12 21:53 dpdklab
2024-02-12 21:52 dpdklab
2024-02-12 21:49 dpdklab
2024-02-12 21:49 dpdklab
2024-02-12 21:47 dpdklab
2024-02-12 21:47 dpdklab
2024-02-12 21:46 dpdklab
2024-02-12 21:45 dpdklab
2024-02-12 21:45 dpdklab
2024-02-12 21:45 dpdklab
2024-02-12 21:45 dpdklab
2024-02-12 21:44 dpdklab
2024-02-12 21:44 dpdklab
2024-02-12 21:44 dpdklab
2024-02-12 21:43 dpdklab
2024-02-12 21:40 dpdklab
2024-02-12 21:39 dpdklab
2024-02-12 21:38 dpdklab
2024-02-12 21:37 dpdklab
2024-02-12 21:37 dpdklab
2024-02-12 21:37 dpdklab
2024-02-12 21:36 dpdklab
2024-02-12 21:36 dpdklab
2024-02-12 21:36 dpdklab
2024-02-12 21:36 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=65ca9146.0d0a0220.3dee9.9b6cSMTPIN_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).