From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142747 [PATCH] [RFC,v2,1/1] devtools: add vscode configu
Date: Mon, 29 Jul 2024 08:53:27 -0700 (PDT) [thread overview]
Message-ID: <66a7baf7.050a0220.18f479.8f98SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <99003582461c7ec772e49dae9b43840496342646.1722258213.git.anatoly.burakov@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142747
_Testing pending_
Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: Monday, July 29 2024 13:05:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:82c47f005b9a0a1e3a649664b7713443d18abe43
142747 --> testing pending
Upstream job id: Windows-Compile-DPDK-Meson#23913
Test environment and result as below:
+---------------------+----------------------+--------------------+-------------------+
| Environment | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+======================+====================+===================+
| Windows Server 2019 | PASS | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Windows Server 2022 | PEND | PASS | PEND |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 13.3 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 14.1 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30643/
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-29 15:53 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99003582461c7ec772e49dae9b43840496342646.1722258213.git.anatoly.burakov@intel.com>
2024-07-29 12:39 ` |SUCCESS| pw142747 [RFC PATCH v2 1/1] devtools: add vscode configuration generator qemudev
2024-07-29 12:43 ` qemudev
2024-07-29 13:06 ` checkpatch
2024-07-29 14:23 ` 0-day Robot
2024-07-29 15:24 ` |PENDING| pw142747 [PATCH] [RFC,v2,1/1] devtools: add vscode configu dpdklab
2024-07-29 15:26 ` |SUCCESS| " dpdklab
2024-07-29 15:28 ` |PENDING| " dpdklab
2024-07-29 15:32 ` |SUCCESS| " dpdklab
2024-07-29 15:34 ` dpdklab
2024-07-29 15:34 ` |PENDING| " dpdklab
2024-07-29 15:40 ` |SUCCESS| " dpdklab
2024-07-29 15:40 ` dpdklab
2024-07-29 15:42 ` dpdklab
2024-07-29 15:44 ` dpdklab
2024-07-29 15:45 ` dpdklab
2024-07-29 15:46 ` dpdklab
2024-07-29 15:48 ` |PENDING| " dpdklab
2024-07-29 15:49 ` dpdklab
2024-07-29 15:49 ` |SUCCESS| " dpdklab
2024-07-29 15:50 ` |PENDING| " dpdklab
2024-07-29 15:53 ` dpdklab [this message]
2024-07-29 15:53 ` |SUCCESS| " dpdklab
2024-07-29 15:53 ` dpdklab
2024-07-29 15:53 ` |PENDING| " dpdklab
2024-07-29 15:54 ` dpdklab
2024-07-29 15:54 ` |SUCCESS| " dpdklab
2024-07-29 15:55 ` dpdklab
2024-07-29 16:05 ` |PENDING| " dpdklab
2024-07-29 16:05 ` dpdklab
2024-07-29 16:06 ` dpdklab
2024-07-29 16:06 ` dpdklab
2024-07-29 16:07 ` dpdklab
2024-07-29 16:08 ` dpdklab
2024-07-29 16:09 ` dpdklab
2024-07-29 16:11 ` dpdklab
2024-07-29 16:12 ` dpdklab
2024-07-29 16:12 ` |SUCCESS| " dpdklab
2024-07-29 16:13 ` |PENDING| " dpdklab
2024-07-29 16:14 ` dpdklab
2024-07-29 16:17 ` dpdklab
2024-07-29 16:17 ` dpdklab
2024-07-29 16:18 ` dpdklab
2024-07-29 16:19 ` dpdklab
2024-07-29 16:20 ` dpdklab
2024-07-29 16:20 ` dpdklab
2024-07-29 16:21 ` dpdklab
2024-07-29 16:21 ` dpdklab
2024-07-29 16:22 ` dpdklab
2024-07-29 16:26 ` dpdklab
2024-07-29 16:26 ` dpdklab
2024-07-29 16:27 ` dpdklab
2024-07-29 16:27 ` dpdklab
2024-07-29 16:27 ` dpdklab
2024-07-29 16:27 ` dpdklab
2024-07-29 16:27 ` dpdklab
2024-07-29 16:28 ` dpdklab
2024-07-29 16:29 ` dpdklab
2024-07-29 16:29 ` dpdklab
2024-07-29 16:29 ` dpdklab
2024-07-29 16:30 ` dpdklab
2024-07-29 16:30 ` dpdklab
2024-07-29 16:31 ` dpdklab
2024-07-29 16:32 ` dpdklab
2024-07-29 16:33 ` dpdklab
2024-07-29 16:36 ` dpdklab
2024-07-29 16:38 ` dpdklab
2024-07-29 16:38 ` dpdklab
2024-07-29 16:39 ` dpdklab
2024-07-29 16:39 ` dpdklab
2024-07-29 16:41 ` dpdklab
2024-07-29 16:42 ` dpdklab
2024-07-29 16:44 ` dpdklab
2024-07-29 16:44 ` dpdklab
2024-07-29 16:46 ` dpdklab
2024-07-29 16:47 ` dpdklab
2024-07-29 16:47 ` dpdklab
2024-07-29 16:50 ` dpdklab
2024-07-29 16:53 ` dpdklab
2024-07-29 16:55 ` dpdklab
2024-07-29 16:56 ` dpdklab
2024-07-29 16:58 ` dpdklab
2024-07-29 16:58 ` |SUCCESS| " dpdklab
2024-07-29 16:59 ` |PENDING| " dpdklab
2024-07-29 17:01 ` dpdklab
2024-07-29 17:05 ` dpdklab
2024-07-29 17:06 ` dpdklab
2024-07-29 17:07 ` dpdklab
2024-07-29 17:08 ` dpdklab
2024-07-29 17:09 ` dpdklab
2024-07-29 17:11 ` dpdklab
2024-07-29 17:14 ` dpdklab
2024-07-29 17:15 ` dpdklab
2024-07-29 17:17 ` dpdklab
2024-07-29 17:21 ` |SUCCESS| " dpdklab
2024-07-29 17:21 ` |PENDING| " dpdklab
2024-07-29 17:22 ` |SUCCESS| " dpdklab
2024-07-29 17:23 ` |PENDING| " dpdklab
2024-07-29 17:26 ` dpdklab
2024-07-29 17:29 ` dpdklab
2024-07-29 17:30 ` dpdklab
2024-07-29 17:30 ` dpdklab
2024-07-29 17:30 ` dpdklab
2024-07-29 17:31 ` dpdklab
2024-07-29 17:31 ` dpdklab
2024-07-29 17:32 ` dpdklab
2024-07-29 17:34 ` dpdklab
2024-07-29 17:35 ` dpdklab
2024-07-29 17:40 ` dpdklab
2024-07-29 17:40 ` dpdklab
2024-07-29 17:46 ` dpdklab
2024-07-29 17:47 ` dpdklab
2024-07-29 17:48 ` dpdklab
2024-07-29 17:48 ` dpdklab
2024-07-29 17:49 ` dpdklab
2024-07-29 18:02 ` |SUCCESS| " dpdklab
2024-07-29 18:03 ` dpdklab
2024-07-29 18:08 ` 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=66a7baf7.050a0220.18f479.8f98SMTPIN_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).