From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142909-142911 [PATCH] [v2,3/3] examples/l3fwd: enhance v
Date: Mon, 05 Aug 2024 23:55:33 -0700 (PDT) [thread overview]
Message-ID: <66b1c8e5.630a0220.9375.aaa2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240806034120.3165295-4-g.singh@nxp.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142911
_Testing pending_
Submitter: Gagandeep Singh <g.singh@nxp.com>
Date: Tuesday, August 06 2024 03:41:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3
142909-142911 --> testing pending
Upstream job id: Windows-Compile-DPDK-Meson#24117
Test environment and result as below:
+---------------------+--------------------+----------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2019 | PASS | PASS | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS | PASS | PASS |
+---------------------+--------------------+----------------------+-------------------+
| 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/30721/
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-08-06 6:55 UTC|newest]
Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240806034120.3165295-4-g.singh@nxp.com>
2024-08-06 3:15 ` |SUCCESS| pw142909-142911 [v2 3/3] examples/l3fwd: enhance valid ports checking qemudev
2024-08-06 3:19 ` qemudev
2024-08-06 3:43 ` |SUCCESS| pw142911 " checkpatch
2024-08-06 4:43 ` 0-day Robot
2024-08-06 5:05 ` |SUCCESS| pw142909-142911 [PATCH] [v2,3/3] examples/l3fwd: enhance v dpdklab
2024-08-06 5:15 ` |PENDING| " dpdklab
2024-08-06 5:23 ` dpdklab
2024-08-06 5:27 ` dpdklab
2024-08-06 5:36 ` dpdklab
2024-08-06 5:36 ` dpdklab
2024-08-06 5:38 ` dpdklab
2024-08-06 5:40 ` dpdklab
2024-08-06 5:44 ` dpdklab
2024-08-06 5:45 ` dpdklab
2024-08-06 5:48 ` dpdklab
2024-08-06 5:52 ` dpdklab
2024-08-06 5:53 ` dpdklab
2024-08-06 5:56 ` dpdklab
2024-08-06 5:59 ` dpdklab
2024-08-06 6:06 ` |SUCCESS| " dpdklab
2024-08-06 6:06 ` dpdklab
2024-08-06 6:06 ` |PENDING| " dpdklab
2024-08-06 6:20 ` |SUCCESS| " dpdklab
2024-08-06 6:38 ` |PENDING| " dpdklab
2024-08-06 6:39 ` dpdklab
2024-08-06 6:40 ` dpdklab
2024-08-06 6:41 ` dpdklab
2024-08-06 6:43 ` dpdklab
2024-08-06 6:46 ` dpdklab
2024-08-06 6:49 ` dpdklab
2024-08-06 6:50 ` dpdklab
2024-08-06 6:51 ` |SUCCESS| " dpdklab
2024-08-06 6:51 ` |PENDING| " dpdklab
2024-08-06 6:52 ` dpdklab
2024-08-06 6:52 ` dpdklab
2024-08-06 6:53 ` dpdklab
2024-08-06 6:54 ` dpdklab
2024-08-06 6:55 ` dpdklab [this message]
2024-08-06 6:56 ` dpdklab
2024-08-06 6:56 ` dpdklab
2024-08-06 6:59 ` |SUCCESS| " dpdklab
2024-08-06 7:01 ` |PENDING| " dpdklab
2024-08-06 7:04 ` dpdklab
2024-08-06 7:04 ` dpdklab
2024-08-06 7:08 ` dpdklab
2024-08-06 7:08 ` |SUCCESS| " dpdklab
2024-08-06 7:11 ` |PENDING| " dpdklab
2024-08-06 7:14 ` dpdklab
2024-08-06 7:16 ` dpdklab
2024-08-06 7:17 ` dpdklab
2024-08-06 7:19 ` dpdklab
2024-08-06 7:22 ` dpdklab
2024-08-06 7:44 ` |SUCCESS| " dpdklab
2024-08-06 7:48 ` |PENDING| " dpdklab
2024-08-06 7:51 ` |SUCCESS| " dpdklab
2024-08-06 7:52 ` |PENDING| " dpdklab
2024-08-06 7:53 ` dpdklab
2024-08-06 7:55 ` dpdklab
2024-08-06 7:57 ` |SUCCESS| " dpdklab
2024-08-06 7:57 ` |PENDING| " dpdklab
2024-08-06 7:57 ` dpdklab
2024-08-06 7:57 ` dpdklab
2024-08-06 7:58 ` dpdklab
2024-08-06 7:59 ` dpdklab
2024-08-06 7:59 ` dpdklab
2024-08-06 7:59 ` dpdklab
2024-08-06 8:00 ` dpdklab
2024-08-06 8:00 ` dpdklab
2024-08-06 8:02 ` |SUCCESS| " dpdklab
2024-08-06 8:05 ` |PENDING| " dpdklab
2024-08-06 8:05 ` dpdklab
2024-08-06 8:05 ` dpdklab
2024-08-06 8:06 ` dpdklab
2024-08-06 8:06 ` dpdklab
2024-08-06 8:07 ` dpdklab
2024-08-06 8:07 ` |SUCCESS| " dpdklab
2024-08-06 8:08 ` |PENDING| " dpdklab
2024-08-06 8:10 ` dpdklab
2024-08-06 8:11 ` dpdklab
2024-08-06 8:11 ` dpdklab
2024-08-06 8:12 ` |SUCCESS| " dpdklab
2024-08-06 8:13 ` |PENDING| " dpdklab
2024-08-06 8:14 ` dpdklab
2024-08-06 8:14 ` dpdklab
2024-08-06 8:17 ` dpdklab
2024-08-06 8:17 ` dpdklab
2024-08-06 8:20 ` dpdklab
2024-08-06 8:21 ` dpdklab
2024-08-06 8:21 ` dpdklab
2024-08-06 8:22 ` dpdklab
2024-08-06 8:22 ` dpdklab
2024-08-06 8:27 ` dpdklab
2024-08-06 8:27 ` |SUCCESS| " dpdklab
2024-08-06 8:28 ` |PENDING| " dpdklab
2024-08-06 8:28 ` dpdklab
2024-08-06 8:29 ` dpdklab
2024-08-06 8:33 ` |SUCCESS| " dpdklab
2024-08-06 8:37 ` |PENDING| " dpdklab
2024-08-06 8:38 ` |SUCCESS| " dpdklab
2024-08-06 8:47 ` |PENDING| " dpdklab
2024-08-06 8:49 ` dpdklab
2024-08-06 8:50 ` dpdklab
2024-08-06 8:51 ` dpdklab
2024-08-06 8:51 ` dpdklab
2024-08-06 9:02 ` |SUCCESS| " dpdklab
2024-08-06 9:16 ` |PENDING| " dpdklab
2024-08-06 9:18 ` dpdklab
2024-08-06 9:25 ` dpdklab
2024-08-06 9:53 ` |SUCCESS| " dpdklab
2024-08-07 1:38 ` dpdklab
2024-08-07 1:46 ` dpdklab
2024-08-07 2:00 ` 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=66b1c8e5.630a0220.9375.aaa2SMTPIN_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).