From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw102046 [PATCH] [v2] net/mlx5: fix meter yellow policy with RSS action
Date: Mon, 18 Oct 2021 16:21:50 -0400 (EDT) [thread overview]
Message-ID: <20211018202150.E7B4160524@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 4974 bytes --]
Test-Label: iol-x86_64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/102046
_Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Monday, October 18 2021 13:53:05
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9942ebb9c698a53b86e2bbd450f3e24238771fe5
102046 --> testing pass
Test environment and result as below:
+---------------------+----------------------+--------------------+-------------------+
| Environment | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_compile_spdk |
+=====================+======================+====================+===================+
| Windows Server 2019 | PASS | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Fedora 31 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 13 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Ubuntu 18.04 | SKIPPED | PASS | PASS |
+---------------------+----------------------+--------------------+-------------------+
| openSUSE Leap 15 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| CentOS 8 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| CentOS Stream 8 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Ubuntu 20.04 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Fedora 32 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| RHEL8 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| RHEL 7 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Arch Linux | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Alpine | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Fedora 34 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Fedora 33 | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
| Fedora 34 clang | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 9.0 and gcc 8.1.0 (MinGW)
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
CentOS 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
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)
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/19505/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-10-18 20:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 20:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-18 22:07 dpdklab
2021-10-18 21:53 dpdklab
2021-10-18 21:44 dpdklab
2021-10-18 21:39 dpdklab
2021-10-18 21:25 dpdklab
2021-10-18 21:11 dpdklab
2021-10-18 20:57 dpdklab
2021-10-18 20:44 dpdklab
2021-10-18 20:32 dpdklab
2021-10-18 20:08 dpdklab
2021-10-18 19:57 dpdklab
2021-10-18 19:45 dpdklab
2021-10-18 18:44 dpdklab
2021-10-18 18:27 dpdklab
2021-10-18 18:23 dpdklab
2021-10-18 18:22 dpdklab
2021-10-18 18:14 dpdklab
2021-10-18 18:10 dpdklab
2021-10-18 18:01 dpdklab
2021-10-18 17:59 dpdklab
2021-10-18 17:50 dpdklab
[not found] <20211018135305.146594-1-bingz@nvidia.com>
2021-10-18 13:54 ` [dpdk-test-report] |SUCCESS| pw102046 [PATCH v2] " checkpatch
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=20211018202150.E7B4160524@noxus.dpdklab.iol.unh.edu \
--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).