From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131806 [PATCH] eal: fix location of per lcore macro docu
Date: Thu, 21 Sep 2023 13:04:44 -0700 (PDT) [thread overview]
Message-ID: <650ca1dc.920a0220.13d5cd.5bbcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131806
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, September 21 2023 18:13:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31e60e81f025e9fffa69b68bffe5cfaa22d5c098
131806 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
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)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-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/27691/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-21 20:04 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 20:04 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-22 1:48 dpdklab
2023-09-22 1:43 dpdklab
2023-09-22 1:40 dpdklab
2023-09-22 1:28 dpdklab
2023-09-21 22:52 dpdklab
2023-09-21 21:35 dpdklab
2023-09-21 21:24 dpdklab
2023-09-21 21:24 dpdklab
2023-09-21 21:06 dpdklab
2023-09-21 21:01 dpdklab
2023-09-21 20:59 dpdklab
2023-09-21 20:54 dpdklab
2023-09-21 20:50 dpdklab
2023-09-21 20:50 dpdklab
2023-09-21 20:45 dpdklab
2023-09-21 20:44 dpdklab
2023-09-21 20:41 dpdklab
2023-09-21 20:40 dpdklab
2023-09-21 20:32 dpdklab
2023-09-21 20:31 dpdklab
2023-09-21 20:27 dpdklab
2023-09-21 20:25 dpdklab
2023-09-21 20:25 dpdklab
2023-09-21 20:24 dpdklab
2023-09-21 20:23 dpdklab
2023-09-21 20:19 dpdklab
2023-09-21 20:17 dpdklab
2023-09-21 20:16 dpdklab
2023-09-21 20:15 dpdklab
2023-09-21 20:14 dpdklab
2023-09-21 20:14 dpdklab
2023-09-21 20:13 dpdklab
2023-09-21 20:13 dpdklab
2023-09-21 20:12 dpdklab
2023-09-21 20:12 dpdklab
2023-09-21 20:11 dpdklab
2023-09-21 20:07 dpdklab
2023-09-21 20:06 dpdklab
2023-09-21 20:05 dpdklab
2023-09-21 20:02 dpdklab
2023-09-21 20:01 dpdklab
2023-09-21 19:49 dpdklab
2023-09-21 19:47 dpdklab
2023-09-21 19:46 dpdklab
2023-09-21 19:45 dpdklab
2023-09-21 19:40 dpdklab
2023-09-21 19:40 dpdklab
2023-09-21 19:29 dpdklab
2023-09-21 19:26 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=650ca1dc.920a0220.13d5cd.5bbcSMTPIN_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).