From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142796 [PATCH] net/gve : Update EOP bit in txd rte_mbuf
Date: Wed, 31 Jul 2024 16:13:21 -0700 (PDT) [thread overview]
Message-ID: <66aac511.050a0220.320fb4.0e5fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1722443901-2400194-1-git-send-email-tathagat.dpdk@gmail.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142796
_Testing pending_
Submitter: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
Date: Wednesday, July 31 2024 16:38:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:37ce4c84c0f23c3989bc7ae19e03a4593cec94e5
142796 --> testing pending
Upstream job id: Windows-Compile-DPDK-Meson#24003
Test environment and result as below:
+---------------------+--------------------+-------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile | dpdk_mingw64_compile |
+=====================+====================+===================+======================+
| Windows Server 2019 | PASS | SKIPPED | PASS |
+---------------------+--------------------+-------------------+----------------------+
| Windows Server 2022 | PASS | 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/30682/
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-31 23:13 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1722443901-2400194-1-git-send-email-tathagat.dpdk@gmail.com>
2024-07-31 16:10 ` |SUCCESS| pw142796 [PATCH] net/gve : Update EOP bit in txd rte_mbuf chain qemudev
2024-07-31 16:14 ` qemudev
2024-07-31 16:37 ` checkpatch
2024-07-31 17:22 ` 0-day Robot
2024-07-31 23:00 ` |SUCCESS| pw142796 [PATCH] net/gve : Update EOP bit in txd rte_mbuf dpdklab
2024-07-31 23:01 ` |PENDING| " dpdklab
2024-07-31 23:03 ` |SUCCESS| " dpdklab
2024-07-31 23:05 ` dpdklab
2024-07-31 23:06 ` |PENDING| " dpdklab
2024-07-31 23:08 ` dpdklab
2024-07-31 23:08 ` |SUCCESS| " dpdklab
2024-07-31 23:09 ` dpdklab
2024-07-31 23:10 ` dpdklab
2024-07-31 23:10 ` |PENDING| " dpdklab
2024-07-31 23:13 ` dpdklab [this message]
2024-07-31 23:15 ` dpdklab
2024-07-31 23:18 ` |SUCCESS| " dpdklab
2024-07-31 23:18 ` |PENDING| " dpdklab
2024-07-31 23:19 ` |SUCCESS| " dpdklab
2024-07-31 23:22 ` dpdklab
2024-07-31 23:22 ` dpdklab
2024-07-31 23:23 ` |PENDING| " dpdklab
2024-07-31 23:24 ` |SUCCESS| " dpdklab
2024-07-31 23:29 ` |PENDING| " dpdklab
2024-07-31 23:43 ` |SUCCESS| " dpdklab
2024-07-31 23:45 ` |PENDING| " dpdklab
2024-08-01 0:40 ` dpdklab
2024-08-01 0:40 ` dpdklab
2024-08-01 0:41 ` dpdklab
2024-08-01 0:48 ` dpdklab
2024-08-01 0:52 ` dpdklab
2024-08-01 0:53 ` dpdklab
2024-08-01 0:54 ` dpdklab
2024-08-01 0:55 ` dpdklab
2024-08-01 1:09 ` dpdklab
2024-08-01 1:10 ` dpdklab
2024-08-01 1:11 ` dpdklab
2024-08-01 1:11 ` dpdklab
2024-08-01 1:14 ` dpdklab
2024-08-01 1:14 ` dpdklab
2024-08-01 1:14 ` dpdklab
2024-08-01 1:16 ` dpdklab
2024-08-01 1:17 ` dpdklab
2024-08-01 1:18 ` dpdklab
2024-08-01 1:19 ` dpdklab
2024-08-01 1:19 ` dpdklab
2024-08-01 1:19 ` dpdklab
2024-08-01 1:19 ` dpdklab
2024-08-01 1:20 ` dpdklab
2024-08-01 1:23 ` dpdklab
2024-08-01 1:28 ` dpdklab
2024-08-01 1:40 ` dpdklab
2024-08-01 1:46 ` |SUCCESS| " dpdklab
2024-08-01 2:19 ` |PENDING| " dpdklab
2024-08-01 2:22 ` |SUCCESS| " dpdklab
2024-08-01 2:24 ` dpdklab
2024-08-01 2:24 ` |PENDING| " dpdklab
2024-08-01 2:25 ` dpdklab
2024-08-01 2:25 ` dpdklab
2024-08-01 2:29 ` |SUCCESS| " dpdklab
2024-08-01 2:32 ` |PENDING| " dpdklab
2024-08-01 2:32 ` dpdklab
2024-08-01 2:32 ` dpdklab
2024-08-01 2:37 ` dpdklab
2024-08-01 2:39 ` dpdklab
2024-08-01 2:44 ` dpdklab
2024-08-01 2:44 ` dpdklab
2024-08-01 2:47 ` dpdklab
2024-08-01 2:48 ` |SUCCESS| " dpdklab
2024-08-01 2:50 ` |PENDING| " dpdklab
2024-08-01 2:51 ` dpdklab
2024-08-01 2:52 ` |SUCCESS| " dpdklab
2024-08-01 2:52 ` |PENDING| " dpdklab
2024-08-01 2:57 ` |SUCCESS| " dpdklab
2024-08-01 2:58 ` dpdklab
2024-08-01 3:17 ` |PENDING| " dpdklab
2024-08-01 3:22 ` |SUCCESS| " dpdklab
2024-08-01 3:23 ` |PENDING| " dpdklab
2024-08-01 3:28 ` dpdklab
2024-08-01 3:32 ` dpdklab
2024-08-01 3:35 ` dpdklab
2024-08-01 3:37 ` dpdklab
2024-08-01 3:43 ` dpdklab
2024-08-01 3:48 ` dpdklab
2024-08-01 3:51 ` dpdklab
2024-08-01 3:53 ` dpdklab
2024-08-01 3:53 ` dpdklab
2024-08-01 3:54 ` dpdklab
2024-08-01 3:55 ` dpdklab
2024-08-01 3:57 ` dpdklab
2024-08-01 4:05 ` dpdklab
2024-08-01 4:07 ` dpdklab
2024-08-01 4:08 ` dpdklab
2024-08-01 4:09 ` dpdklab
2024-08-01 4:09 ` dpdklab
2024-08-01 4:13 ` dpdklab
2024-08-01 4:13 ` dpdklab
2024-08-01 4:15 ` dpdklab
2024-08-01 4:16 ` dpdklab
2024-08-01 4:17 ` dpdklab
2024-08-01 4:20 ` dpdklab
2024-08-01 4:20 ` dpdklab
2024-08-01 4:21 ` dpdklab
2024-08-01 4:21 ` dpdklab
2024-08-01 4:22 ` dpdklab
2024-08-01 4:22 ` dpdklab
2024-08-01 4:23 ` dpdklab
2024-08-01 4:26 ` dpdklab
2024-08-01 4:44 ` dpdklab
2024-08-01 4:51 ` |SUCCESS| " dpdklab
2024-08-01 4:59 ` dpdklab
2024-08-01 5:00 ` dpdklab
2024-08-02 10:58 ` 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=66aac511.050a0220.320fb4.0e5fSMTPIN_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).