From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| pw128447-128449 [PATCH] [3/3] net/nfp: fix flow hash table
Date: Fri, 09 Jun 2023 00:10:00 -0700 (PDT) [thread overview]
Message-ID: <6482d048.170a0220.e4034.5206SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/128449
_Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Friday, June 09 2023 06:01:00
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:e5cb7ea1f4c45fa147442a248dce0fdffd907291
128447-128449 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| RHEL 7 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
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)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26602/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-09 7:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 7:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-10 15:54 dpdklab
2023-06-09 16:36 dpdklab
2023-06-09 16:32 dpdklab
2023-06-09 16:22 dpdklab
2023-06-09 16:17 dpdklab
2023-06-09 16:02 dpdklab
2023-06-09 10:33 dpdklab
2023-06-09 10:32 dpdklab
2023-06-09 7:44 dpdklab
2023-06-09 7:36 dpdklab
2023-06-09 7:27 dpdklab
2023-06-09 7:13 dpdklab
2023-06-09 7:13 dpdklab
2023-06-09 7:07 dpdklab
2023-06-09 7:07 dpdklab
2023-06-09 7:05 dpdklab
2023-06-09 7:03 dpdklab
2023-06-09 7:01 dpdklab
2023-06-09 7:01 dpdklab
2023-06-09 7:00 dpdklab
2023-06-09 6:59 dpdklab
2023-06-09 6:56 dpdklab
2023-06-09 6:48 dpdklab
2023-06-09 6:40 dpdklab
2023-06-09 6:40 dpdklab
2023-06-09 6:40 dpdklab
2023-06-09 6:40 dpdklab
2023-06-09 6:39 dpdklab
2023-06-09 6:39 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=6482d048.170a0220.e4034.5206SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.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).