From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142577 [PATCH] [v2] ethdev: fix device init without sock
Date: Mon, 22 Jul 2024 06:34:47 -0700 (PDT) [thread overview]
Message-ID: <669e5ff7.050a0220.dc89a.0bceSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240722100228.618616-1-bruce.richardson@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142577
_Testing pending_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Monday, July 22 2024 10:02:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7ead15fca71bff435a22638bf5a0baf27520bd06
142577 --> testing pending
Upstream job id: Windows-Compile-DPDK-Mingw64#20904
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS | PEND |
+---------------------+--------------------+----------------------+
| FreeBSD 13.3 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 14.1 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PEND | PASS |
+---------------------+--------------------+----------------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30572/
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-07-22 13:34 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240722100228.618616-1-bruce.richardson@intel.com>
2024-07-22 9:41 ` |SUCCESS| pw142577 [PATCH v2] ethdev: fix device init without socket-local memory qemudev
2024-07-22 9:45 ` qemudev
2024-07-22 10:08 ` checkpatch
2024-07-22 11:03 ` 0-day Robot
2024-07-22 12:40 ` |PENDING| pw142577 [PATCH] [v2] ethdev: fix device init without sock dpdklab
2024-07-22 12:51 ` |SUCCESS| " dpdklab
2024-07-22 13:02 ` dpdklab
2024-07-22 13:03 ` dpdklab
2024-07-22 13:11 ` dpdklab
2024-07-22 13:13 ` dpdklab
2024-07-22 13:19 ` |PENDING| " dpdklab
2024-07-22 13:22 ` |SUCCESS| " dpdklab
2024-07-22 13:22 ` dpdklab
2024-07-22 13:23 ` |PENDING| " dpdklab
2024-07-22 13:24 ` |SUCCESS| " dpdklab
2024-07-22 13:25 ` |PENDING| " dpdklab
2024-07-22 13:27 ` dpdklab
2024-07-22 13:27 ` dpdklab
2024-07-22 13:28 ` |SUCCESS| " dpdklab
2024-07-22 13:29 ` |PENDING| " dpdklab
2024-07-22 13:30 ` |SUCCESS| " dpdklab
2024-07-22 13:30 ` |PENDING| " dpdklab
2024-07-22 13:31 ` dpdklab
2024-07-22 13:32 ` dpdklab
2024-07-22 13:34 ` dpdklab [this message]
2024-07-22 13:35 ` dpdklab
2024-07-22 13:36 ` dpdklab
2024-07-22 13:39 ` dpdklab
2024-07-22 13:40 ` dpdklab
2024-07-22 13:43 ` |SUCCESS| " dpdklab
2024-07-22 13:45 ` |PENDING| " dpdklab
2024-07-22 13:47 ` |SUCCESS| " dpdklab
2024-07-22 13:51 ` |PENDING| " dpdklab
2024-07-22 13:53 ` dpdklab
2024-07-22 13:53 ` dpdklab
2024-07-22 13:54 ` dpdklab
2024-07-22 13:57 ` dpdklab
2024-07-22 13:58 ` dpdklab
2024-07-22 13:58 ` dpdklab
2024-07-22 13:58 ` dpdklab
2024-07-22 13:59 ` dpdklab
2024-07-22 13:59 ` dpdklab
2024-07-22 14:05 ` |SUCCESS| " dpdklab
2024-07-22 14:10 ` |PENDING| " dpdklab
2024-07-22 14:10 ` dpdklab
2024-07-22 14:10 ` dpdklab
2024-07-22 14:11 ` dpdklab
2024-07-22 14:12 ` dpdklab
2024-07-22 14:14 ` |SUCCESS| " dpdklab
2024-07-22 14:15 ` |PENDING| " dpdklab
2024-07-22 14:18 ` dpdklab
2024-07-22 14:19 ` |SUCCESS| " dpdklab
2024-07-22 14:21 ` |PENDING| " dpdklab
2024-07-22 14:22 ` dpdklab
2024-07-22 14:24 ` dpdklab
2024-07-22 14:35 ` dpdklab
2024-07-22 14:36 ` dpdklab
2024-07-22 14:37 ` dpdklab
2024-07-22 14:38 ` |SUCCESS| " dpdklab
2024-07-22 14:39 ` |PENDING| " dpdklab
2024-07-22 14:40 ` dpdklab
2024-07-22 14:41 ` dpdklab
2024-07-22 14:41 ` dpdklab
2024-07-22 14:41 ` dpdklab
2024-07-22 14:41 ` dpdklab
2024-07-22 14:42 ` dpdklab
2024-07-22 14:42 ` dpdklab
2024-07-22 14:43 ` dpdklab
2024-07-22 14:44 ` dpdklab
2024-07-22 14:51 ` |SUCCESS| " dpdklab
2024-07-22 14:51 ` |PENDING| " dpdklab
2024-07-22 14:51 ` dpdklab
2024-07-22 14:52 ` dpdklab
2024-07-22 14:52 ` dpdklab
2024-07-22 14:54 ` dpdklab
2024-07-22 14:55 ` dpdklab
2024-07-22 14:59 ` dpdklab
2024-07-22 15:01 ` dpdklab
2024-07-22 15:02 ` dpdklab
2024-07-22 15:03 ` dpdklab
2024-07-22 15:04 ` dpdklab
2024-07-22 15:05 ` dpdklab
2024-07-22 15:07 ` dpdklab
2024-07-22 15:07 ` dpdklab
2024-07-22 15:09 ` dpdklab
2024-07-22 15:11 ` dpdklab
2024-07-22 15:11 ` dpdklab
2024-07-22 15:12 ` dpdklab
2024-07-22 15:13 ` dpdklab
2024-07-22 15:15 ` dpdklab
2024-07-22 15:16 ` dpdklab
2024-07-22 15:18 ` dpdklab
2024-07-22 15:23 ` dpdklab
2024-07-22 15:24 ` dpdklab
2024-07-22 15:25 ` dpdklab
2024-07-22 15:26 ` dpdklab
2024-07-22 15:27 ` dpdklab
2024-07-22 15:28 ` dpdklab
2024-07-22 15:28 ` dpdklab
2024-07-22 15:29 ` dpdklab
2024-07-22 15:31 ` dpdklab
2024-07-22 15:31 ` dpdklab
2024-07-22 15:31 ` |SUCCESS| " dpdklab
2024-07-22 15:32 ` |PENDING| " dpdklab
2024-07-22 15:35 ` dpdklab
2024-07-22 15:37 ` |SUCCESS| " dpdklab
2024-07-22 15:37 ` dpdklab
2024-07-22 15:37 ` |PENDING| " dpdklab
2024-07-22 15:47 ` dpdklab
2024-07-22 15:49 ` |SUCCESS| " dpdklab
2024-07-22 15:54 ` |PENDING| " dpdklab
2024-07-22 15:58 ` |SUCCESS| " dpdklab
2024-07-22 16:10 ` |PENDING| " dpdklab
2024-07-22 16:13 ` dpdklab
2024-07-22 16:27 ` |SUCCESS| " dpdklab
2024-07-23 14:47 ` 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=669e5ff7.050a0220.dc89a.0bceSMTPIN_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).