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| pw122664-122674 [PATCH] [V2, 10/10] net/hns3: fix incorrect check for duplicate RSS rule
Date: Mon, 30 Jan 2023 12:18:52 +0000 (UTC) [thread overview]
Message-ID: <20230130121852.797E460BE4@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 4912 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/122674
_Testing PASS_
Submitter: Dongdong Liu <liudongdong3@huawei.com>
Date: Monday, January 30 2023 09:31:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a211079a92e962bbd0ec81e425a6ffc32890e67
122664-122674 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+----------------------+----------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_unit_test |
+========================================+====================+======================+================+
| Windows Server 2019 | PASS | PASS | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| FreeBSD 13 | PASS | SKIPPED | SKIPPED |
+----------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 ARM Clang Native | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 ARM GCC Native | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| CentOS Stream 8 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| openSUSE Leap 15 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Debian Buster | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS | SKIPPED | SKIPPED |
+----------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 22.04 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| CentOS Stream 9 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| RHEL 7 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| Debian Bullseye | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
| RHEL8 | PASS | SKIPPED | PASS |
+----------------------------------------+--------------------+----------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25114/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-01-30 12:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 12:18 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-30 13:14 dpdklab
2023-01-30 13:00 dpdklab
2023-01-30 12:59 dpdklab
2023-01-30 12:19 dpdklab
2023-01-30 12:18 dpdklab
2023-01-30 12:06 dpdklab
2023-01-30 11:51 dpdklab
2023-01-30 11:50 dpdklab
2023-01-30 11:48 dpdklab
2023-01-30 11:25 dpdklab
2023-01-30 10:21 dpdklab
2023-01-30 10:16 dpdklab
2023-01-30 10:13 dpdklab
2023-01-30 10:10 dpdklab
2023-01-30 10:09 dpdklab
2023-01-30 10:07 dpdklab
2023-01-30 10:06 dpdklab
2023-01-30 10:00 dpdklab
[not found] <20230130093129.18529-11-liudongdong3@huawei.com>
2023-01-30 9:26 ` |SUCCESS| pw122664-122674 [PATCH V2 " qemudev
2023-01-30 9:30 ` 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=20230130121852.797E460BE4@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).