From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135772 [PATCH] [v11] gro: fix reordering of packets in G
Date: Sun, 07 Jan 2024 09:25:52 -0800 (PST) [thread overview]
Message-ID: <659adea0.050a0220.8a289.ee2aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135772
_Functional Testing PASS_
Submitter: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Date: Sunday, January 07 2024 11:29:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135772 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28815/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-07 17:25 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 17:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-07 20:24 dpdklab
2024-01-07 19:57 dpdklab
2024-01-07 19:24 dpdklab
2024-01-07 19:07 dpdklab
2024-01-07 19:03 dpdklab
2024-01-07 18:55 dpdklab
2024-01-07 18:55 dpdklab
2024-01-07 18:54 dpdklab
2024-01-07 18:53 dpdklab
2024-01-07 18:53 dpdklab
2024-01-07 18:52 dpdklab
2024-01-07 18:50 dpdklab
2024-01-07 18:34 dpdklab
2024-01-07 18:32 dpdklab
2024-01-07 18:32 dpdklab
2024-01-07 18:31 dpdklab
2024-01-07 18:30 dpdklab
2024-01-07 18:26 dpdklab
2024-01-07 18:24 dpdklab
2024-01-07 18:18 dpdklab
2024-01-07 18:16 dpdklab
2024-01-07 18:15 dpdklab
2024-01-07 18:13 dpdklab
2024-01-07 18:13 dpdklab
2024-01-07 18:12 dpdklab
2024-01-07 18:12 dpdklab
2024-01-07 18:11 dpdklab
2024-01-07 18:11 dpdklab
2024-01-07 18:11 dpdklab
2024-01-07 18:10 dpdklab
2024-01-07 18:10 dpdklab
2024-01-07 18:10 dpdklab
2024-01-07 18:10 dpdklab
2024-01-07 18:10 dpdklab
2024-01-07 18:09 dpdklab
2024-01-07 18:08 dpdklab
2024-01-07 18:08 dpdklab
2024-01-07 18:08 dpdklab
2024-01-07 18:08 dpdklab
2024-01-07 18:07 dpdklab
2024-01-07 18:07 dpdklab
2024-01-07 18:07 dpdklab
2024-01-07 18:07 dpdklab
2024-01-07 18:06 dpdklab
2024-01-07 18:06 dpdklab
2024-01-07 18:05 dpdklab
2024-01-07 18:04 dpdklab
2024-01-07 18:04 dpdklab
2024-01-07 18:02 dpdklab
2024-01-07 17:59 dpdklab
2024-01-07 17:59 dpdklab
2024-01-07 17:59 dpdklab
2024-01-07 17:58 dpdklab
2024-01-07 17:58 dpdklab
2024-01-07 17:56 dpdklab
2024-01-07 17:56 dpdklab
2024-01-07 17:55 dpdklab
2024-01-07 17:55 dpdklab
2024-01-07 17:46 dpdklab
2024-01-07 17:32 dpdklab
2024-01-07 17:30 dpdklab
2024-01-07 17:29 dpdklab
2024-01-07 17:27 dpdklab
2024-01-07 17:25 dpdklab
2024-01-07 17:21 dpdklab
2024-01-07 17:19 dpdklab
2024-01-07 17:10 dpdklab
2024-01-07 17:06 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=659adea0.050a0220.8a289.ee2aSMTPIN_ADDED_MISSING@mx.google.com \
--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).