From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136878 [PATCH] [v12] net/iavf: add diagnostic support in
Date: Mon, 19 Feb 2024 19:29:00 -0800 (PST) [thread overview]
Message-ID: <65d41c7c.250a0220.c35d1.8362SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136878
_Testing PASS_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Monday, February 19 2024 09:55:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4e7732d6c4c64514dc26c3cc0203d19851b5f5aa
136878 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29182/
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-20 3:29 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 3:29 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 6:50 dpdklab
2024-02-20 20:22 dpdklab
2024-02-20 5:25 dpdklab
2024-02-20 5:24 dpdklab
2024-02-20 5:05 dpdklab
2024-02-20 5:01 dpdklab
2024-02-20 5:00 dpdklab
2024-02-20 4:54 dpdklab
2024-02-20 4:44 dpdklab
2024-02-20 4:44 dpdklab
2024-02-20 4:31 dpdklab
2024-02-20 4:24 dpdklab
2024-02-20 4:17 dpdklab
2024-02-20 4:14 dpdklab
2024-02-20 4:13 dpdklab
2024-02-20 4:01 dpdklab
2024-02-20 3:57 dpdklab
2024-02-20 3:56 dpdklab
2024-02-20 3:54 dpdklab
2024-02-20 3:45 dpdklab
2024-02-20 3:42 dpdklab
2024-02-20 3:38 dpdklab
2024-02-20 3:38 dpdklab
2024-02-20 3:36 dpdklab
2024-02-20 3:36 dpdklab
2024-02-20 3:35 dpdklab
2024-02-20 3:35 dpdklab
2024-02-20 3:35 dpdklab
2024-02-20 3:34 dpdklab
2024-02-20 3:34 dpdklab
2024-02-20 3:33 dpdklab
2024-02-20 3:29 dpdklab
2024-02-20 3:28 dpdklab
2024-02-20 3:28 dpdklab
2024-02-20 3:27 dpdklab
2024-02-20 3:25 dpdklab
2024-02-20 3:24 dpdklab
2024-02-20 3:23 dpdklab
2024-02-20 3:21 dpdklab
2024-02-20 3:21 dpdklab
2024-02-20 3:21 dpdklab
2024-02-20 3:20 dpdklab
2024-02-20 3:19 dpdklab
2024-02-20 3:18 dpdklab
2024-02-20 3:14 dpdklab
2024-02-20 3:14 dpdklab
2024-02-20 3:14 dpdklab
2024-02-20 3:14 dpdklab
2024-02-20 3:13 dpdklab
2024-02-20 3:12 dpdklab
2024-02-20 3:12 dpdklab
2024-02-20 3:09 dpdklab
2024-02-20 3:09 dpdklab
2024-02-20 3:08 dpdklab
2024-02-20 3:07 dpdklab
2024-02-20 3:03 dpdklab
2024-02-20 3:02 dpdklab
2024-02-20 3:01 dpdklab
2024-02-20 3:00 dpdklab
2024-02-20 2:56 dpdklab
2024-02-20 2:54 dpdklab
2024-02-20 2:54 dpdklab
2024-02-20 2:49 dpdklab
2024-02-20 2:48 dpdklab
2024-02-20 2:48 dpdklab
2024-02-20 2:47 dpdklab
2024-02-20 2:45 dpdklab
2024-02-20 2:44 dpdklab
2024-02-20 2:44 dpdklab
2024-02-20 2:41 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=65d41c7c.250a0220.c35d1.8362SMTPIN_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).