From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Dongdong Liu <liudongdong3@huawei.com>,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125861-125867 [PATCH] [7/7] net/hns3: support getting current FEC capability from firmware
Date: Sat, 8 Apr 2023 03:32:10 +0000 (UTC) [thread overview]
Message-ID: <20230408033210.D2CEE6012C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125867
_Testing PASS_
Submitter: Dongdong Liu <liudongdong3@huawei.com>
Date: Saturday, April 08 2023 02:27:39
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:65487b12db83c9ef37526a983c43191cd44dae99
125861-125867 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 8 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: clang 14.0.5-1.fc36
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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/25942/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-08 3:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 3:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-08 4:04 dpdklab
2023-04-08 4:02 dpdklab
2023-04-08 3:52 dpdklab
2023-04-08 3:35 dpdklab
2023-04-08 3:35 dpdklab
2023-04-08 3:32 dpdklab
2023-04-08 3:32 dpdklab
2023-04-08 3:31 dpdklab
2023-04-08 3:29 dpdklab
2023-04-08 3:28 dpdklab
2023-04-08 3:28 dpdklab
2023-04-08 3:28 dpdklab
2023-04-08 3:26 dpdklab
2023-04-08 3:25 dpdklab
2023-04-08 3:24 dpdklab
2023-04-08 3:23 dpdklab
2023-04-08 3:20 dpdklab
2023-04-08 3:15 dpdklab
2023-04-08 3:15 dpdklab
2023-04-08 3:15 dpdklab
2023-04-08 3:12 dpdklab
2023-04-08 3:11 dpdklab
2023-04-08 3:11 dpdklab
2023-04-08 3:08 dpdklab
2023-04-08 3:04 dpdklab
2023-04-08 3:03 dpdklab
2023-04-08 3:02 dpdklab
[not found] <20230408022740.14522-8-liudongdong3@huawei.com>
2023-04-08 2:22 ` |SUCCESS| pw125861-125867 [PATCH 7/7] " qemudev
2023-04-08 2:26 ` qemudev
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=20230408033210.D2CEE6012C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=liudongdong3@huawei.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).