From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142522 [PATCH] net/gve: Update Rx/Tx functions for RTE_P
Date: Thu, 18 Jul 2024 23:40:35 -0700 (PDT) [thread overview]
Message-ID: <669a0a63.050a0220.306cd.26baSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1721363814-2387892-1-git-send-email-tathagat.dpdk@gmail.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142522
_Testing pending_
Submitter: priyadarshitathagat <tathagat.dpdk@gmail.com>
Date: Friday, July 19 2024 04:36:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d32d6c8e31923c3a1eeebe7da6ded89332830576
142522 --> testing pending
Upstream job id: Windows-Compile-DPDK-Meson#23655
Test environment and result as below:
+---------------------+--------------------+----------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2019 | PASS | PEND | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PEND | PEND | PEND |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1 | PEND | SKIPPED | 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/30561/
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-19 6:55 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1721363814-2387892-1-git-send-email-tathagat.dpdk@gmail.com>
2024-07-19 4:11 ` |SUCCESS| pw142522 [PATCH] net/gve: Update Rx/Tx functions for RTE_PROC_SECONDARY qemudev
2024-07-19 4:16 ` qemudev
2024-07-19 4:39 ` |WARNING| " checkpatch
2024-07-19 5:23 ` |SUCCESS| " 0-day Robot
2024-07-19 5:47 ` |SUCCESS| pw142522 [PATCH] net/gve: Update Rx/Tx functions for RTE_P dpdklab
2024-07-19 5:52 ` dpdklab
2024-07-19 6:00 ` dpdklab
2024-07-19 6:03 ` dpdklab
2024-07-19 6:05 ` dpdklab
2024-07-19 6:08 ` dpdklab
2024-07-19 6:15 ` dpdklab
2024-07-19 6:19 ` |PENDING| " dpdklab
2024-07-19 6:21 ` dpdklab
2024-07-19 6:27 ` dpdklab
2024-07-19 6:29 ` dpdklab
2024-07-19 6:30 ` dpdklab
2024-07-19 6:31 ` dpdklab
2024-07-19 6:35 ` dpdklab
2024-07-19 6:36 ` |SUCCESS| " dpdklab
2024-07-19 6:37 ` |PENDING| " dpdklab
2024-07-19 6:40 ` dpdklab [this message]
2024-07-19 6:43 ` dpdklab
2024-07-19 6:44 ` dpdklab
2024-07-19 6:44 ` dpdklab
2024-07-19 6:47 ` dpdklab
2024-07-19 6:52 ` |SUCCESS| " dpdklab
2024-07-19 6:52 ` |PENDING| " dpdklab
2024-07-19 6:54 ` |SUCCESS| " dpdklab
2024-07-19 6:58 ` |PENDING| " dpdklab
2024-07-19 6:58 ` dpdklab
2024-07-19 6:59 ` |SUCCESS| " dpdklab
2024-07-19 6:59 ` |PENDING| " dpdklab
2024-07-19 7:00 ` dpdklab
2024-07-19 7:06 ` |SUCCESS| " dpdklab
2024-07-19 7:06 ` |PENDING| " dpdklab
2024-07-19 7:07 ` dpdklab
2024-07-19 7:07 ` dpdklab
2024-07-19 7:08 ` dpdklab
2024-07-19 7:11 ` dpdklab
2024-07-19 7:24 ` dpdklab
2024-07-19 7:26 ` dpdklab
2024-07-19 7:28 ` dpdklab
2024-07-19 7:31 ` dpdklab
2024-07-19 7:34 ` dpdklab
2024-07-19 7:34 ` dpdklab
2024-07-19 7:34 ` dpdklab
2024-07-19 7:36 ` dpdklab
2024-07-19 7:41 ` |SUCCESS| " dpdklab
2024-07-19 7:44 ` |PENDING| " dpdklab
2024-07-19 7:46 ` dpdklab
2024-07-19 7:52 ` dpdklab
2024-07-19 7:54 ` dpdklab
2024-07-19 7:55 ` dpdklab
2024-07-19 7:56 ` dpdklab
2024-07-19 8:00 ` dpdklab
2024-07-19 8:00 ` dpdklab
2024-07-19 8:01 ` dpdklab
2024-07-19 8:03 ` dpdklab
2024-07-19 8:05 ` dpdklab
2024-07-19 8:05 ` dpdklab
2024-07-19 8:07 ` dpdklab
2024-07-19 8:07 ` dpdklab
2024-07-19 8:08 ` dpdklab
2024-07-19 8:08 ` dpdklab
2024-07-19 8:09 ` dpdklab
2024-07-19 8:15 ` |SUCCESS| " dpdklab
2024-07-19 8:20 ` |PENDING| " dpdklab
2024-07-19 8:25 ` |SUCCESS| " dpdklab
2024-07-19 8:29 ` |PENDING| " dpdklab
2024-07-19 8:29 ` |SUCCESS| " dpdklab
2024-07-19 8:31 ` |PENDING| " dpdklab
2024-07-19 8:33 ` dpdklab
2024-07-19 8:35 ` dpdklab
2024-07-19 8:35 ` |SUCCESS| " dpdklab
2024-07-19 8:38 ` |PENDING| " dpdklab
2024-07-19 8:40 ` |SUCCESS| " dpdklab
2024-07-19 8:45 ` dpdklab
2024-07-19 8:46 ` |PENDING| " dpdklab
2024-07-19 8:46 ` dpdklab
2024-07-19 8:47 ` dpdklab
2024-07-19 8:50 ` |SUCCESS| " dpdklab
2024-07-19 8:50 ` |PENDING| " dpdklab
2024-07-19 8:53 ` dpdklab
2024-07-19 8:53 ` dpdklab
2024-07-19 8:56 ` dpdklab
2024-07-19 9:05 ` dpdklab
2024-07-19 9:07 ` dpdklab
2024-07-19 9:09 ` dpdklab
2024-07-19 9:11 ` dpdklab
2024-07-19 9:20 ` dpdklab
2024-07-19 9:22 ` dpdklab
2024-07-19 9:23 ` dpdklab
2024-07-19 9:26 ` dpdklab
2024-07-19 9:26 ` dpdklab
2024-07-19 9:31 ` dpdklab
2024-07-19 9:34 ` dpdklab
2024-07-19 9:35 ` dpdklab
2024-07-19 9:41 ` dpdklab
2024-07-19 9:41 ` dpdklab
2024-07-19 9:43 ` dpdklab
2024-07-19 9:45 ` dpdklab
2024-07-19 9:46 ` dpdklab
2024-07-19 9:51 ` dpdklab
2024-07-19 9:53 ` dpdklab
2024-07-19 9:57 ` |SUCCESS| " dpdklab
2024-07-19 10:01 ` |PENDING| " dpdklab
2024-07-19 10:02 ` dpdklab
2024-07-19 10:03 ` dpdklab
2024-07-19 10:03 ` dpdklab
2024-07-19 10:04 ` |SUCCESS| " dpdklab
2024-07-19 10:05 ` dpdklab
2024-07-19 10:05 ` dpdklab
2024-07-19 10:40 ` 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=669a0a63.050a0220.306cd.26baSMTPIN_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).