From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125972 [PATCH] [v2] net/mlx5: fix lro update tcp header cksum error
Date: Thu, 13 Apr 2023 02:37:04 +0000 (UTC) [thread overview]
Message-ID: <20230413023704.AEB5A60095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125972
_Testing PASS_
Submitter: jiangheng (G) <jiangheng14@huawei.com>
Date: Thursday, April 13 2023 00:57:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
125972 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| RHEL 7 | PASS |
+-----------------+----------+
| CentOS Stream 8 | 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 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25976/
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-13 2:37 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 2:37 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-13 7:23 dpdklab
2023-04-13 7:23 dpdklab
2023-04-13 6:19 dpdklab
2023-04-13 6:19 dpdklab
2023-04-13 3:18 dpdklab
2023-04-13 3:18 dpdklab
2023-04-13 3:16 dpdklab
2023-04-13 3:14 dpdklab
2023-04-13 3:13 dpdklab
2023-04-13 3:09 dpdklab
2023-04-13 3:06 dpdklab
2023-04-13 3:04 dpdklab
2023-04-13 2:57 dpdklab
2023-04-13 2:56 dpdklab
2023-04-13 2:56 dpdklab
2023-04-13 2:54 dpdklab
2023-04-13 2:51 dpdklab
2023-04-13 2:49 dpdklab
2023-04-13 2:49 dpdklab
2023-04-13 2:48 dpdklab
2023-04-13 2:45 dpdklab
2023-04-13 2:44 dpdklab
2023-04-13 2:43 dpdklab
2023-04-13 2:42 dpdklab
2023-04-13 2:42 dpdklab
2023-04-13 2:28 dpdklab
2023-04-13 2:26 dpdklab
2023-04-13 2:25 dpdklab
2023-04-13 2:23 dpdklab
2023-04-13 2:22 dpdklab
2023-04-13 2:20 dpdklab
2023-04-13 2:19 dpdklab
2023-04-13 2:17 dpdklab
2023-04-13 2:16 dpdklab
2023-04-13 2:16 dpdklab
2023-04-13 2:15 dpdklab
2023-04-13 2:14 dpdklab
2023-04-13 2:13 dpdklab
2023-04-13 2:08 dpdklab
2023-04-13 2:06 dpdklab
2023-04-13 2:03 dpdklab
2023-04-13 2:00 dpdklab
2023-04-13 1:59 dpdklab
2023-04-13 1:57 dpdklab
2023-04-13 1:56 dpdklab
2023-04-13 1:56 dpdklab
2023-04-13 1:55 dpdklab
2023-04-13 1:54 dpdklab
2023-04-13 1:51 dpdklab
2023-04-13 1:51 dpdklab
2023-04-13 1:50 dpdklab
2023-04-13 1:42 dpdklab
2023-04-13 1:36 dpdklab
2023-04-13 1:33 dpdklab
2023-04-13 1:33 dpdklab
2023-04-13 1:29 dpdklab
2023-04-13 1:29 dpdklab
2023-04-13 1:22 dpdklab
[not found] <46433ee3531547aebf906e4144c520d1@huawei.com>
2023-04-13 0:47 ` |SUCCESS| pw125972 [PATCH v2] " qemudev
2023-04-13 0:51 ` qemudev
2023-04-13 2:18 ` 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=20230413023704.AEB5A60095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.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).