From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143737 [PATCH] eal/x86: fix 32-bit write-combined stores
Date: Fri, 06 Sep 2024 12:37:29 -0700 (PDT) [thread overview]
Message-ID: <66db59f9.170a0220.1dc5e0.7fa3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240906132757.457921-1-bruce.richardson@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/143737
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, September 06 2024 13:27:57
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
143737 --> testing pass
Upstream job id: Windows-Compile-DPDK-Native#22005
Test environment and result as below:
+---------------------+--------------------+----------------------+-----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_win_llvm_compile |
+=====================+====================+======================+=======================+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-----------------------+
| FreeBSD 14.1 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-----------------------+
| Windows Server 2022 | SKIPPED | PASS | PASS |
+---------------------+--------------------+----------------------+-----------------------+
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
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30940/
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-06 19:37 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240906132757.457921-1-bruce.richardson@intel.com>
2024-09-06 13:11 ` qemudev
2024-09-06 13:15 ` qemudev
2024-09-06 13:30 ` checkpatch
2024-09-06 14:25 ` 0-day Robot
2024-09-06 18:40 ` dpdklab
2024-09-06 19:11 ` dpdklab
2024-09-06 19:28 ` dpdklab
2024-09-06 19:37 ` dpdklab [this message]
2024-09-06 20:06 ` |PENDING| " dpdklab
2024-09-06 21:02 ` dpdklab
2024-09-06 21:32 ` |SUCCESS| " dpdklab
2024-09-06 21:34 ` dpdklab
2024-09-06 21:48 ` dpdklab
2024-09-06 21:52 ` |PENDING| " dpdklab
2024-09-06 22:16 ` dpdklab
2024-09-07 0:00 ` |SUCCESS| " dpdklab
2024-09-07 0:40 ` dpdklab
2024-09-07 1:27 ` dpdklab
2024-09-07 3:03 ` dpdklab
2024-09-07 3:51 ` dpdklab
2024-09-07 5:38 ` dpdklab
2024-09-07 5:43 ` dpdklab
2024-09-07 6:02 ` dpdklab
2024-09-07 6:09 ` dpdklab
2024-09-07 6:17 ` dpdklab
2024-09-07 6:21 ` dpdklab
2024-09-07 6:25 ` dpdklab
2024-09-07 6:29 ` dpdklab
2024-09-07 6:49 ` dpdklab
2024-09-07 11:25 ` dpdklab
2024-09-07 11:25 ` dpdklab
2024-09-07 11:44 ` |PENDING| " dpdklab
2024-09-07 12:19 ` dpdklab
2024-09-07 12:22 ` |SUCCESS| " dpdklab
2024-09-07 12:22 ` dpdklab
2024-09-07 13:25 ` dpdklab
2024-09-07 13:58 ` dpdklab
2024-09-07 17:28 ` dpdklab
2024-09-08 7:48 ` dpdklab
2024-09-08 8:22 ` dpdklab
2024-09-17 4:46 ` dpdklab
2024-09-17 5:05 ` dpdklab
2024-09-17 5:17 ` dpdklab
2024-09-17 5: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=66db59f9.170a0220.1dc5e0.7fa3SMTPIN_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).