From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135943 [PATCH] [v3] gro : packets not getting flushed in
Date: Wed, 17 Jan 2024 21:48:58 -0800 (PST) [thread overview]
Message-ID: <65a8bbca.050a0220.4134a.3373SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135943
_Functional Testing PASS_
Submitter: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Date: Wednesday, January 17 2024 20:20:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39a8b1251b204d3898b4c462184f60bda1b64698
135943 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28892/
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-18 5:49 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 5:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-18 17:15 dpdklab
2024-01-18 13:01 dpdklab
2024-01-18 9:39 dpdklab
2024-01-18 8:45 dpdklab
2024-01-18 8:44 dpdklab
2024-01-18 8:43 dpdklab
2024-01-18 8:42 dpdklab
2024-01-18 8:40 dpdklab
2024-01-18 8:16 dpdklab
2024-01-18 8:15 dpdklab
2024-01-18 8:14 dpdklab
2024-01-18 8:12 dpdklab
2024-01-18 8:12 dpdklab
2024-01-18 8:08 dpdklab
2024-01-18 8:06 dpdklab
2024-01-18 8:06 dpdklab
2024-01-18 8:04 dpdklab
2024-01-18 8:04 dpdklab
2024-01-18 8:03 dpdklab
2024-01-18 7:55 dpdklab
2024-01-18 7:55 dpdklab
2024-01-18 7:54 dpdklab
2024-01-18 7:53 dpdklab
2024-01-18 7:52 dpdklab
2024-01-18 7:51 dpdklab
2024-01-18 7:51 dpdklab
2024-01-18 7:50 dpdklab
2024-01-18 7:47 dpdklab
2024-01-18 7:46 dpdklab
2024-01-18 7:46 dpdklab
2024-01-18 7:45 dpdklab
2024-01-18 7:45 dpdklab
2024-01-18 7:44 dpdklab
2024-01-18 7:43 dpdklab
2024-01-18 7:42 dpdklab
2024-01-18 7:42 dpdklab
2024-01-18 7:35 dpdklab
2024-01-18 7:33 dpdklab
2024-01-18 7:08 dpdklab
2024-01-18 6:52 dpdklab
2024-01-18 6:52 dpdklab
2024-01-18 6:51 dpdklab
2024-01-18 6:49 dpdklab
2024-01-18 6:48 dpdklab
2024-01-18 6:47 dpdklab
2024-01-18 6:46 dpdklab
2024-01-18 6:45 dpdklab
2024-01-18 6:33 dpdklab
2024-01-18 6:07 dpdklab
2024-01-18 5:53 dpdklab
2024-01-18 5:53 dpdklab
2024-01-18 5:51 dpdklab
2024-01-18 5:49 dpdklab
2024-01-18 5:48 dpdklab
2024-01-18 5:47 dpdklab
2024-01-18 5:47 dpdklab
2024-01-18 5:47 dpdklab
2024-01-18 5:46 dpdklab
2024-01-18 5:45 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=65a8bbca.050a0220.4134a.3373SMTPIN_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).