From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137111-137146 [PATCH] [v5,39/39] ip_frag: use C11 aligna
Date: Fri, 23 Feb 2024 14:06:19 -0800 (PST) [thread overview]
Message-ID: <65d916db.170a0220.560da.06ebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137146
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Friday, February 23 2024 19:04:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137111-137146 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29249/
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-23 22:06 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 22:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-24 5:26 dpdklab
2024-02-24 5:08 dpdklab
2024-02-24 4:51 dpdklab
2024-02-23 23:41 dpdklab
2024-02-23 23:33 dpdklab
2024-02-23 23:32 dpdklab
2024-02-23 23:31 dpdklab
2024-02-23 23:24 dpdklab
2024-02-23 23:17 dpdklab
2024-02-23 22:55 dpdklab
2024-02-23 22:46 dpdklab
2024-02-23 22:45 dpdklab
2024-02-23 22:43 dpdklab
2024-02-23 22:31 dpdklab
2024-02-23 22:29 dpdklab
2024-02-23 22:27 dpdklab
2024-02-23 22:26 dpdklab
2024-02-23 22:25 dpdklab
2024-02-23 22:23 dpdklab
2024-02-23 22:23 dpdklab
2024-02-23 22:22 dpdklab
2024-02-23 22:20 dpdklab
2024-02-23 22:12 dpdklab
2024-02-23 22:10 dpdklab
2024-02-23 22:06 dpdklab
2024-02-23 22:05 dpdklab
2024-02-23 22:04 dpdklab
2024-02-23 22:03 dpdklab
2024-02-23 21:58 dpdklab
2024-02-23 21:54 dpdklab
2024-02-23 21:54 dpdklab
2024-02-23 21:53 dpdklab
2024-02-23 21:53 dpdklab
2024-02-23 21:43 dpdklab
2024-02-23 21:42 dpdklab
2024-02-23 21:39 dpdklab
2024-02-23 21:39 dpdklab
2024-02-23 21:39 dpdklab
2024-02-23 21:38 dpdklab
2024-02-23 21:35 dpdklab
2024-02-23 21:35 dpdklab
2024-02-23 21:34 dpdklab
2024-02-23 21:33 dpdklab
2024-02-23 21:31 dpdklab
2024-02-23 21:27 dpdklab
2024-02-23 21:25 dpdklab
2024-02-23 21:25 dpdklab
2024-02-23 21:24 dpdklab
2024-02-23 21:24 dpdklab
2024-02-23 21:23 dpdklab
2024-02-23 21:22 dpdklab
2024-02-23 21:22 dpdklab
2024-02-23 21:22 dpdklab
2024-02-23 21:21 dpdklab
2024-02-23 21:15 dpdklab
2024-02-23 21:13 dpdklab
2024-02-23 21:13 dpdklab
2024-02-23 21:13 dpdklab
2024-02-23 21:13 dpdklab
2024-02-23 21:13 dpdklab
2024-02-23 21:12 dpdklab
2024-02-23 21:12 dpdklab
2024-02-23 21:12 dpdklab
2024-02-23 21:11 dpdklab
2024-02-23 21:11 dpdklab
2024-02-23 21:10 dpdklab
2024-02-23 20:57 dpdklab
2024-02-23 20:54 dpdklab
2024-02-23 20:54 dpdklab
2024-02-23 20:51 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=65d916db.170a0220.560da.06ebSMTPIN_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).