From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Simei Su <simei.su@intel.com>
Subject: |SUCCESS| pw135623 [PATCH] net/i40e: updated 23.11 recommended match
Date: Thu, 28 Dec 2023 06:46:23 -0800 (PST) [thread overview]
Message-ID: <658d8a3f.050a0220.7c28f.0a61SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135623
_Testing PASS_
Submitter: Simei Su <simei.su@intel.com>
Date: Thursday, December 28 2023 08:37:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135623 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | 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
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28748/
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-28 14:46 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 14:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-28 16:16 dpdklab
2023-12-28 15:58 dpdklab
2023-12-28 15:39 dpdklab
2023-12-28 15:21 dpdklab
2023-12-28 15:21 dpdklab
2023-12-28 15:20 dpdklab
2023-12-28 15:07 dpdklab
2023-12-28 15:05 dpdklab
2023-12-28 15:05 dpdklab
2023-12-28 15:04 dpdklab
2023-12-28 15:00 dpdklab
2023-12-28 15:00 dpdklab
2023-12-28 14:59 dpdklab
2023-12-28 14:59 dpdklab
2023-12-28 14:59 dpdklab
2023-12-28 14:58 dpdklab
2023-12-28 14:58 dpdklab
2023-12-28 14:58 dpdklab
2023-12-28 14:57 dpdklab
2023-12-28 14:57 dpdklab
2023-12-28 14:55 dpdklab
2023-12-28 14:52 dpdklab
2023-12-28 14:51 dpdklab
2023-12-28 14:51 dpdklab
2023-12-28 14:51 dpdklab
2023-12-28 14:51 dpdklab
2023-12-28 14:50 dpdklab
2023-12-28 14:50 dpdklab
2023-12-28 14:50 dpdklab
2023-12-28 14:50 dpdklab
2023-12-28 14:49 dpdklab
2023-12-28 14:49 dpdklab
2023-12-28 14:49 dpdklab
2023-12-28 14:48 dpdklab
2023-12-28 14:47 dpdklab
2023-12-28 14:46 dpdklab
2023-12-28 14:45 dpdklab
2023-12-28 14:45 dpdklab
2023-12-28 14:38 dpdklab
2023-12-28 14:32 dpdklab
2023-12-28 14:32 dpdklab
2023-12-28 14:31 dpdklab
2023-12-28 14:29 dpdklab
2023-12-28 14:29 dpdklab
2023-12-28 14:29 dpdklab
2023-12-28 14:28 dpdklab
2023-12-28 14:26 dpdklab
2023-12-28 14:26 dpdklab
2023-12-28 14:26 dpdklab
2023-12-28 14:25 dpdklab
2023-12-28 14:20 dpdklab
2023-12-28 14:20 dpdklab
2023-12-28 14:20 dpdklab
2023-12-28 14:19 dpdklab
2023-12-28 14:18 dpdklab
2023-12-28 14:18 dpdklab
2023-12-28 14:12 dpdklab
2023-12-28 14:12 dpdklab
2023-12-28 14:12 dpdklab
2023-12-28 14:05 dpdklab
2023-12-28 14:03 dpdklab
2023-12-28 14:03 dpdklab
2023-12-28 14:03 dpdklab
2023-12-28 13:55 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=658d8a3f.050a0220.7c28f.0a61SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=simei.su@intel.com \
--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).