From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135335-135336 [PATCH] [2/2] ip_frag: updated name for IP
Date: Tue, 19 Dec 2023 07:58:09 -0800 (PST) [thread overview]
Message-ID: <6581bd91.c80a0220.be13f.da41SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135336
_Testing PASS_
Submitter: Euan Bourke <euan.bourke@intel.com>
Date: Tuesday, December 19 2023 15:17:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135335-135336 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28684/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-19 15:58 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 15:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-19 18:50 dpdklab
2023-12-19 17:47 dpdklab
2023-12-19 17:41 dpdklab
2023-12-19 17:11 dpdklab
2023-12-19 16:55 dpdklab
2023-12-19 16:52 dpdklab
2023-12-19 16:51 dpdklab
2023-12-19 16:51 dpdklab
2023-12-19 16:51 dpdklab
2023-12-19 16:51 dpdklab
2023-12-19 16:48 dpdklab
2023-12-19 16:46 dpdklab
2023-12-19 16:44 dpdklab
2023-12-19 16:43 dpdklab
2023-12-19 16:43 dpdklab
2023-12-19 16:41 dpdklab
2023-12-19 16:40 dpdklab
2023-12-19 16:39 dpdklab
2023-12-19 16:38 dpdklab
2023-12-19 16:38 dpdklab
2023-12-19 16:37 dpdklab
2023-12-19 16:37 dpdklab
2023-12-19 16:36 dpdklab
2023-12-19 16:35 dpdklab
2023-12-19 16:35 dpdklab
2023-12-19 16:34 dpdklab
2023-12-19 16:34 dpdklab
2023-12-19 16:33 dpdklab
2023-12-19 16:33 dpdklab
2023-12-19 16:32 dpdklab
2023-12-19 16:32 dpdklab
2023-12-19 16:31 dpdklab
2023-12-19 16:31 dpdklab
2023-12-19 16:30 dpdklab
2023-12-19 16:30 dpdklab
2023-12-19 16:30 dpdklab
2023-12-19 16:30 dpdklab
2023-12-19 16:28 dpdklab
2023-12-19 16:25 dpdklab
2023-12-19 16:18 dpdklab
2023-12-19 16:17 dpdklab
2023-12-19 16:17 dpdklab
2023-12-19 16:17 dpdklab
2023-12-19 16:17 dpdklab
2023-12-19 16:12 dpdklab
2023-12-19 16:11 dpdklab
2023-12-19 16:11 dpdklab
2023-12-19 16:11 dpdklab
2023-12-19 16:08 dpdklab
2023-12-19 16:08 dpdklab
2023-12-19 16:06 dpdklab
2023-12-19 16:04 dpdklab
2023-12-19 16:04 dpdklab
2023-12-19 16:04 dpdklab
2023-12-19 16:03 dpdklab
2023-12-19 16:03 dpdklab
2023-12-19 16:03 dpdklab
2023-12-19 16:01 dpdklab
2023-12-19 16:01 dpdklab
2023-12-19 16:00 dpdklab
2023-12-19 15:58 dpdklab
2023-12-19 15:57 dpdklab
2023-12-19 15:57 dpdklab
2023-12-19 15:56 dpdklab
2023-12-19 15:55 dpdklab
2023-12-19 15:55 dpdklab
2023-12-19 15:55 dpdklab
2023-12-19 15:54 dpdklab
2023-12-19 15:54 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=6581bd91.c80a0220.be13f.da41SMTPIN_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).