From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126185-126199 [PATCH] [v7, 14/14] eal: do not define typeof macro when building with MSVC
Date: Tue, 18 Apr 2023 05:46:23 +0000 (UTC) [thread overview]
Message-ID: <20230418054623.0CAA760095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126199
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Monday, April 17 2023 16:10:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126185-126199 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26019/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-18 5:46 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 5:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 4:13 dpdklab
2023-04-18 4:13 dpdklab
2023-04-18 3:52 dpdklab
2023-04-18 3:51 dpdklab
2023-04-18 3:51 dpdklab
2023-04-18 3:25 dpdklab
2023-04-17 22:33 dpdklab
2023-04-17 21:54 dpdklab
2023-04-17 21:51 dpdklab
2023-04-17 21:49 dpdklab
2023-04-17 21:41 dpdklab
2023-04-17 21:36 dpdklab
2023-04-17 21:32 dpdklab
2023-04-17 21:20 dpdklab
2023-04-17 21:18 dpdklab
2023-04-17 21:17 dpdklab
2023-04-17 21:15 dpdklab
2023-04-17 21:15 dpdklab
2023-04-17 20:49 dpdklab
2023-04-17 20:32 dpdklab
2023-04-17 20:32 dpdklab
2023-04-17 20:31 dpdklab
2023-04-17 20:30 dpdklab
2023-04-17 20:28 dpdklab
2023-04-17 20:28 dpdklab
2023-04-17 20:26 dpdklab
2023-04-17 20:22 dpdklab
2023-04-17 19:58 dpdklab
2023-04-17 19:51 dpdklab
2023-04-17 19:47 dpdklab
2023-04-17 19:45 dpdklab
2023-04-17 19:43 dpdklab
2023-04-17 19:43 dpdklab
2023-04-17 19:38 dpdklab
2023-04-17 19:36 dpdklab
2023-04-17 19:34 dpdklab
2023-04-17 19:31 dpdklab
2023-04-17 19:31 dpdklab
2023-04-17 19:30 dpdklab
2023-04-17 19:27 dpdklab
2023-04-17 19:25 dpdklab
2023-04-17 19:18 dpdklab
2023-04-17 19:08 dpdklab
2023-04-17 19:06 dpdklab
2023-04-17 19:05 dpdklab
2023-04-17 19:03 dpdklab
2023-04-17 19:00 dpdklab
2023-04-17 18:59 dpdklab
2023-04-17 18:49 dpdklab
2023-04-17 18:48 dpdklab
2023-04-17 18:47 dpdklab
2023-04-17 18:45 dpdklab
2023-04-17 18:40 dpdklab
[not found] <1681747838-12778-15-git-send-email-roretzla@linux.microsoft.com>
2023-04-17 16:02 ` |SUCCESS| pw126185-126199 [PATCH v7 " qemudev
2023-04-17 16:06 ` qemudev
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=20230418054623.0CAA760095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).