From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw143321 [PATCH] mbuf: add transport mode ESP packet type
Date: Thu, 22 Aug 2024 09:22:26 -0700 (PDT) [thread overview]
Message-ID: <66c765c2.050a0220.3d9941.4389SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240822153218.3782170-1-akozyrev@nvidia.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/143321
_Testing pending_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Thursday, August 22 2024 15:32:18
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143321 --> testing pending
Upstream job id: Generic-VM-DPDK-Compile-Meson#28876
Test environment and result as below:
+---------------------+--------------------+-----------------------+-------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_win_llvm_compile | dpdk_msvc_compile | dpdk_mingw64_compile |
+=====================+====================+=======================+===================+======================+
| FreeBSD 13.3 | PEND | SKIPPED | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+-------------------+----------------------+
| FreeBSD 14.1 | PASS | SKIPPED | SKIPPED | SKIPPED |
+---------------------+--------------------+-----------------------+-------------------+----------------------+
| Windows Server 2022 | SKIPPED | PEND | PEND | PEND |
+---------------------+--------------------+-----------------------+-------------------+----------------------+
FreeBSD 13.3
Kernel: 13.3-RELEASE-p5
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1-RELEASE-p3
Compiler: clang 18.1.5
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30834/
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-22 16:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240822153218.3782170-1-akozyrev@nvidia.com>
2024-08-22 15:07 ` |SUCCESS| " qemudev
2024-08-22 15:11 ` qemudev
2024-08-22 15:33 ` checkpatch
2024-08-22 16:18 ` dpdklab
2024-08-22 16:19 ` dpdklab
2024-08-22 16:22 ` dpdklab [this message]
2024-08-22 16:23 ` 0-day Robot
2024-08-22 16:33 ` |PENDING| " dpdklab
2024-08-22 16:37 ` |SUCCESS| " dpdklab
2024-08-22 16:38 ` dpdklab
2024-08-22 16:43 ` dpdklab
2024-08-22 16:44 ` dpdklab
2024-08-22 17:16 ` |PENDING| " dpdklab
2024-08-22 17:24 ` |SUCCESS| " dpdklab
2024-08-22 17:27 ` dpdklab
2024-08-22 17:27 ` dpdklab
2024-08-22 17:28 ` dpdklab
2024-08-22 17:31 ` dpdklab
2024-08-22 18:23 ` dpdklab
2024-08-22 18:24 ` dpdklab
2024-08-22 18:26 ` dpdklab
2024-08-22 18:26 ` dpdklab
2024-08-22 18:28 ` dpdklab
2024-08-22 18:32 ` dpdklab
2024-08-22 18:44 ` dpdklab
2024-08-22 18:44 ` dpdklab
2024-08-22 20:59 ` dpdklab
2024-08-22 23:44 ` 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=66c765c2.050a0220.3d9941.4389SMTPIN_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).