From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125457 [PATCH] net/mlx5/hws: fix IPv4 frag matching
Date: Thu, 23 Mar 2023 16:56:14 +0000 (UTC) [thread overview]
Message-ID: <20230323165614.F030660125@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125457
_Testing PASS_
Submitter: Alex Vesker <valex@nvidia.com>
Date: Thursday, March 23 2023 12:34:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1a80f6062cf74e4b689b8b9a4f905a24efec527a
125457 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| Ubuntu 20.04 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 12.2.1-2
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25852/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-23 16:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 16:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-25 14:17 dpdklab
2023-03-25 13:20 dpdklab
2023-03-24 3:31 dpdklab
2023-03-24 3:19 dpdklab
2023-03-23 17:55 dpdklab
2023-03-23 16:16 dpdklab
2023-03-23 15:53 dpdklab
2023-03-23 15:43 dpdklab
2023-03-23 15:41 dpdklab
2023-03-23 15:36 dpdklab
2023-03-23 15:33 dpdklab
2023-03-23 15:27 dpdklab
2023-03-23 15:26 dpdklab
2023-03-23 15:24 dpdklab
2023-03-23 15:21 dpdklab
2023-03-23 15:20 dpdklab
2023-03-23 15:16 dpdklab
2023-03-23 15:15 dpdklab
2023-03-23 15:14 dpdklab
2023-03-23 15:08 dpdklab
2023-03-23 15:02 dpdklab
2023-03-23 14:57 dpdklab
2023-03-23 14:56 dpdklab
2023-03-23 14:55 dpdklab
2023-03-23 14:53 dpdklab
2023-03-23 14:46 dpdklab
2023-03-23 14:42 dpdklab
2023-03-23 14:36 dpdklab
2023-03-23 14:29 dpdklab
[not found] <20230323123416.26636-3-valex@nvidia.com>
2023-03-23 12:24 ` qemudev
2023-03-23 12:28 ` qemudev
2023-03-23 13:59 ` 0-day Robot
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=20230323165614.F030660125@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).