From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Mingjin Ye <mingjinx.ye@intel.com>
Subject: |SUCCESS| pw135629-135630 [PATCH] [v6,2/2] net/iavf: add diagnostic
Date: Fri, 29 Dec 2023 03:00:26 -0800 (PST) [thread overview]
Message-ID: <658ea6ca.050a0220.89782.e7acSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135630
_Testing PASS_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Friday, December 29 2023 10:11:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135629-135630 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| Windows Server 2022 | PASS |
+---------------------+--------------------+
| Debian Buster | PASS |
+---------------------+--------------------+
| FreeBSD 13 | PASS |
+---------------------+--------------------+
| CentOS Stream 9 | PASS |
+---------------------+--------------------+
| Windows Server 2019 | PASS |
+---------------------+--------------------+
| Debian Bullseye | PASS |
+---------------------+--------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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/28753/
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-29 11:00 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 11:00 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-29 13:49 dpdklab
2023-12-29 11:54 dpdklab
2023-12-29 11:53 dpdklab
2023-12-29 11:40 dpdklab
2023-12-29 11:38 dpdklab
2023-12-29 11:38 dpdklab
2023-12-29 11:37 dpdklab
2023-12-29 11:36 dpdklab
2023-12-29 11:33 dpdklab
2023-12-29 11:33 dpdklab
2023-12-29 11:31 dpdklab
2023-12-29 11:29 dpdklab
2023-12-29 11:29 dpdklab
2023-12-29 11:27 dpdklab
2023-12-29 11:27 dpdklab
2023-12-29 11:25 dpdklab
2023-12-29 11:25 dpdklab
2023-12-29 11:24 dpdklab
2023-12-29 11:24 dpdklab
2023-12-29 11:21 dpdklab
2023-12-29 11:20 dpdklab
2023-12-29 11:17 dpdklab
2023-12-29 11:16 dpdklab
2023-12-29 11:16 dpdklab
2023-12-29 11:16 dpdklab
2023-12-29 11:15 dpdklab
2023-12-29 11:13 dpdklab
2023-12-29 11:13 dpdklab
2023-12-29 11:12 dpdklab
2023-12-29 11:11 dpdklab
2023-12-29 11:11 dpdklab
2023-12-29 11:10 dpdklab
2023-12-29 11:10 dpdklab
2023-12-29 11:09 dpdklab
2023-12-29 11:09 dpdklab
2023-12-29 11:09 dpdklab
2023-12-29 11:09 dpdklab
2023-12-29 11:08 dpdklab
2023-12-29 11:08 dpdklab
2023-12-29 11:07 dpdklab
2023-12-29 11:06 dpdklab
2023-12-29 11:06 dpdklab
2023-12-29 11:06 dpdklab
2023-12-29 11:05 dpdklab
2023-12-29 11:05 dpdklab
2023-12-29 11:05 dpdklab
2023-12-29 11:05 dpdklab
2023-12-29 11:05 dpdklab
2023-12-29 11:05 dpdklab
2023-12-29 11:04 dpdklab
2023-12-29 11:04 dpdklab
2023-12-29 11:04 dpdklab
2023-12-29 11:04 dpdklab
2023-12-29 11:04 dpdklab
2023-12-29 11:03 dpdklab
2023-12-29 11:03 dpdklab
2023-12-29 11:03 dpdklab
2023-12-29 11:02 dpdklab
2023-12-29 11:02 dpdklab
2023-12-29 11:02 dpdklab
2023-12-29 11:02 dpdklab
2023-12-29 11:01 dpdklab
2023-12-29 11:01 dpdklab
2023-12-29 11:00 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=658ea6ca.050a0220.89782.e7acSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=mingjinx.ye@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).