From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143936 [PATCH] [RFC] doc: restructure the introduction
Date: Wed, 11 Sep 2024 01:42:36 -0700 (PDT) [thread overview]
Message-ID: <66e157fc.6b0a0220.16bf4b.2d58SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240911042800.9203-1-stephen@networkplumber.org>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/143936
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, September 11 2024 04:27:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
143936 --> testing pass
Upstream job id: Windows-Compile-DPDK-VS#3066
Test environment and result as below:
+---------------------+----------------------+-----------------------+--------------------+-------------------+
| Environment | dpdk_mingw64_compile | dpdk_win_llvm_compile | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+======================+=======================+====================+===================+
| Windows Server 2022 | PASS | PASS | SKIPPED | PASS |
+---------------------+----------------------+-----------------------+--------------------+-------------------+
| FreeBSD 13.3 | SKIPPED | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+-----------------------+--------------------+-------------------+
| FreeBSD 14.1 | SKIPPED | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+-----------------------+--------------------+-------------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
FreeBSD 13.3
Kernel: 13.3-RELEASE-p5
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1-RELEASE-p3
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30996/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-09-11 8:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240911042800.9203-1-stephen@networkplumber.org>
2024-09-11 4:07 ` |SUCCESS| pw143936 " qemudev
2024-09-11 4:11 ` qemudev
2024-09-11 4:29 ` |WARNING| " checkpatch
2024-09-11 5:24 ` |SUCCESS| " 0-day Robot
2024-09-11 7:36 ` |SUCCESS| pw143936 [PATCH] " dpdklab
2024-09-11 7:40 ` dpdklab
2024-09-11 7:46 ` dpdklab
2024-09-11 7:56 ` dpdklab
2024-09-11 7:56 ` dpdklab
2024-09-11 8:11 ` |PENDING| " dpdklab
2024-09-11 8:42 ` dpdklab [this message]
2024-09-11 8:54 ` dpdklab
2024-09-11 12:55 ` |SUCCESS| " dpdklab
2024-09-11 14:55 ` dpdklab
2024-09-11 15:01 ` |PENDING| " dpdklab
2024-09-11 15:33 ` |SUCCESS| " dpdklab
2024-09-11 18:25 ` dpdklab
2024-09-11 18:29 ` dpdklab
2024-09-11 18:33 ` dpdklab
2024-09-11 18:37 ` dpdklab
2024-09-11 18:47 ` dpdklab
2024-09-11 18:57 ` dpdklab
2024-09-11 19:01 ` dpdklab
2024-09-12 0:26 ` dpdklab
2024-09-15 17:56 ` dpdklab
2024-09-15 23:14 ` 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=66e157fc.6b0a0220.16bf4b.2d58SMTPIN_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).