From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136754-136791 [PATCH] [v4,39/39] ip_frag: use C11 aligna
Date: Wed, 14 Feb 2024 13:58:55 -0800 (PST) [thread overview]
Message-ID: <65cd379f.170a0220.92ad6.8033SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136791
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, February 14 2024 16:36:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8d85afb19af706de662e7ee686e6e437f835c6e3
136754-136791 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29150/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-14 21:58 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 21:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 23:32 dpdklab
2024-02-14 23:28 dpdklab
2024-02-14 23:23 dpdklab
2024-02-14 23:22 dpdklab
2024-02-14 23:09 dpdklab
2024-02-14 22:59 dpdklab
2024-02-14 22:56 dpdklab
2024-02-14 22:50 dpdklab
2024-02-14 22:47 dpdklab
2024-02-14 22:42 dpdklab
2024-02-14 22:37 dpdklab
2024-02-14 22:32 dpdklab
2024-02-14 22:31 dpdklab
2024-02-14 22:28 dpdklab
2024-02-14 22:26 dpdklab
2024-02-14 22:21 dpdklab
2024-02-14 22:21 dpdklab
2024-02-14 22:20 dpdklab
2024-02-14 22:20 dpdklab
2024-02-14 22:19 dpdklab
2024-02-14 22:18 dpdklab
2024-02-14 22:16 dpdklab
2024-02-14 22:16 dpdklab
2024-02-14 22:16 dpdklab
2024-02-14 22:15 dpdklab
2024-02-14 22:15 dpdklab
2024-02-14 22:14 dpdklab
2024-02-14 22:13 dpdklab
2024-02-14 22:13 dpdklab
2024-02-14 22:12 dpdklab
2024-02-14 22:12 dpdklab
2024-02-14 22:11 dpdklab
2024-02-14 22:10 dpdklab
2024-02-14 22:09 dpdklab
2024-02-14 22:09 dpdklab
2024-02-14 22:08 dpdklab
2024-02-14 22:05 dpdklab
2024-02-14 22:05 dpdklab
2024-02-14 22:03 dpdklab
2024-02-14 22:02 dpdklab
2024-02-14 22:01 dpdklab
2024-02-14 22:01 dpdklab
2024-02-14 22:01 dpdklab
2024-02-14 21:59 dpdklab
2024-02-14 21:59 dpdklab
2024-02-14 21:59 dpdklab
2024-02-14 21:59 dpdklab
2024-02-14 21:58 dpdklab
2024-02-14 21:58 dpdklab
2024-02-14 21:57 dpdklab
2024-02-14 21:57 dpdklab
2024-02-14 21:57 dpdklab
2024-02-14 21:56 dpdklab
2024-02-14 21:56 dpdklab
2024-02-14 21:56 dpdklab
2024-02-14 21:56 dpdklab
2024-02-14 21:56 dpdklab
2024-02-14 21:55 dpdklab
2024-02-14 21:54 dpdklab
2024-02-14 21:54 dpdklab
2024-02-14 21:53 dpdklab
2024-02-14 21:51 dpdklab
2024-02-14 21:51 dpdklab
2024-02-14 21:49 dpdklab
2024-02-14 21:48 dpdklab
2024-02-14 21:24 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=65cd379f.170a0220.92ad6.8033SMTPIN_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).