From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142751 [PATCH] [v1] net/cpfl: fix cpfl parser issue
Date: Tue, 30 Jul 2024 00:17:42 -0700 (PDT) [thread overview]
Message-ID: <66a89396.050a0220.df18d.1deeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240730050952.837611-1-praveen.shetty@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142751
_Testing pending_
Submitter: Praveen Shetty <praveen.shetty@intel.com>
Date: Tuesday, July 30 2024 05:09:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b017bdc4c25e2cd6733a9363e9c566b95834cc4
142751 --> testing pending
Upstream job id: Windows-Compile-DPDK-Meson#23936
Test environment and result as below:
+---------------------+--------------------+-------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile | dpdk_mingw64_compile |
+=====================+====================+===================+======================+
| Windows Server 2019 | PASS | SKIPPED | PEND |
+---------------------+--------------------+-------------------+----------------------+
| Windows Server 2022 | PEND | PEND | PEND |
+---------------------+--------------------+-------------------+----------------------+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------------+
| FreeBSD 14.1 | PASS | 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/30647/
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-30 14:11 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240730050952.837611-1-praveen.shetty@intel.com>
2024-07-30 5:01 ` |SUCCESS| pw142751 [PATCH v1] " qemudev
2024-07-30 5:05 ` qemudev
2024-07-30 5:13 ` checkpatch
2024-07-30 6:02 ` 0-day Robot
2024-07-30 7:07 ` |SUCCESS| pw142751 [PATCH] [v1] " dpdklab
2024-07-30 7:10 ` dpdklab
2024-07-30 7:13 ` |PENDING| " dpdklab
2024-07-30 7:14 ` |SUCCESS| " dpdklab
2024-07-30 7:17 ` dpdklab [this message]
2024-07-30 7:18 ` dpdklab
2024-07-30 7:18 ` |PENDING| " dpdklab
2024-07-30 7:22 ` |SUCCESS| " dpdklab
2024-07-30 7:24 ` |PENDING| " dpdklab
2024-07-30 7:26 ` dpdklab
2024-07-30 7:28 ` |SUCCESS| " dpdklab
2024-07-30 7:29 ` |PENDING| " dpdklab
2024-07-30 7:32 ` |SUCCESS| " dpdklab
2024-07-30 7:32 ` dpdklab
2024-07-30 7:33 ` |PENDING| " dpdklab
2024-07-30 7:34 ` dpdklab
2024-07-30 7:35 ` dpdklab
2024-07-30 7:35 ` |SUCCESS| " dpdklab
2024-07-30 7:36 ` |PENDING| " dpdklab
2024-07-30 7:36 ` dpdklab
2024-07-30 7:38 ` dpdklab
2024-07-30 7:40 ` dpdklab
2024-07-30 7:44 ` dpdklab
2024-07-30 7:44 ` dpdklab
2024-07-30 7:48 ` dpdklab
2024-07-30 7:48 ` |SUCCESS| " dpdklab
2024-07-30 7:49 ` |PENDING| " dpdklab
2024-07-30 7:50 ` dpdklab
2024-07-30 7:52 ` dpdklab
2024-07-30 7:52 ` dpdklab
2024-07-30 7:53 ` dpdklab
2024-07-30 7:53 ` dpdklab
2024-07-30 7:56 ` dpdklab
2024-07-30 8:00 ` dpdklab
2024-07-30 8:05 ` dpdklab
2024-07-30 8:06 ` dpdklab
2024-07-30 8:10 ` |SUCCESS| " dpdklab
2024-07-30 8:11 ` dpdklab
2024-07-30 8:12 ` dpdklab
2024-07-30 8:13 ` |PENDING| " dpdklab
2024-07-30 8:15 ` dpdklab
2024-07-30 8:16 ` dpdklab
2024-07-30 8:20 ` dpdklab
2024-07-30 8:20 ` dpdklab
2024-07-30 8:23 ` dpdklab
2024-07-30 8:23 ` dpdklab
2024-07-30 8:24 ` dpdklab
2024-07-30 8:25 ` dpdklab
2024-07-30 8:26 ` dpdklab
2024-07-30 8:28 ` dpdklab
2024-07-30 8:28 ` dpdklab
2024-07-30 8:30 ` dpdklab
2024-07-30 8:31 ` |FAILURE| " dpdklab
2024-07-30 8:32 ` |SUCCESS| " dpdklab
2024-07-30 8:32 ` |PENDING| " dpdklab
2024-07-30 8:34 ` dpdklab
2024-07-30 8:34 ` |FAILURE| " dpdklab
2024-07-30 8:34 ` |PENDING| " dpdklab
2024-07-30 8:35 ` dpdklab
2024-07-30 8:36 ` dpdklab
2024-07-30 8:37 ` dpdklab
2024-07-30 8:37 ` |FAILURE| " dpdklab
2024-07-30 8:37 ` |PENDING| " dpdklab
2024-07-30 8:37 ` |FAILURE| " dpdklab
2024-07-30 8:39 ` dpdklab
2024-07-30 8:41 ` dpdklab
2024-07-30 8:43 ` |PENDING| " dpdklab
2024-07-30 8:43 ` |FAILURE| " dpdklab
2024-07-30 8:43 ` dpdklab
2024-07-30 8:45 ` dpdklab
2024-07-30 8:47 ` dpdklab
2024-07-30 8:48 ` dpdklab
2024-07-30 8:49 ` dpdklab
2024-07-30 8:51 ` dpdklab
2024-07-30 8:51 ` dpdklab
2024-07-30 8:52 ` dpdklab
2024-07-30 8:52 ` dpdklab
2024-07-30 8:54 ` dpdklab
2024-07-30 8:55 ` dpdklab
2024-07-30 8:56 ` |SUCCESS| " dpdklab
2024-07-30 8:57 ` |FAILURE| " dpdklab
2024-07-30 8:58 ` dpdklab
2024-07-30 8:58 ` dpdklab
2024-07-30 8:58 ` dpdklab
2024-07-30 8:59 ` dpdklab
2024-07-30 8:59 ` dpdklab
2024-07-30 9:00 ` dpdklab
2024-07-30 9:00 ` |PENDING| " dpdklab
2024-07-30 9:01 ` |SUCCESS| " dpdklab
2024-07-30 9:01 ` |FAILURE| " dpdklab
2024-07-30 9:02 ` dpdklab
2024-07-30 9:03 ` dpdklab
2024-07-30 9:04 ` |PENDING| " dpdklab
2024-07-30 9:05 ` |FAILURE| " dpdklab
2024-07-30 9:05 ` dpdklab
2024-07-30 9:05 ` |SUCCESS| " dpdklab
2024-07-30 9:06 ` dpdklab
2024-07-30 9:07 ` |FAILURE| " dpdklab
2024-07-30 9:08 ` |WARNING| " dpdklab
2024-07-30 9:10 ` |SUCCESS| " dpdklab
2024-07-30 9:10 ` dpdklab
2024-07-30 9:16 ` |PENDING| " dpdklab
2024-07-30 9:17 ` |FAILURE| " dpdklab
2024-07-30 9:25 ` dpdklab
2024-07-30 9:29 ` |SUCCESS| " dpdklab
2024-07-30 9:30 ` |PENDING| " dpdklab
2024-07-30 9:46 ` dpdklab
2024-07-30 9:47 ` |SUCCESS| " dpdklab
2024-07-30 9:49 ` 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=66a89396.050a0220.df18d.1deeSMTPIN_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).