From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136585 [PATCH] [v6] gro : packets not getting flushed in
Date: Sat, 10 Feb 2024 23:03:43 -0800 (PST) [thread overview]
Message-ID: <65c8714f.250a0220.8bb7f.0109SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136585
_Testing PASS_
Submitter: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Date: Sunday, February 11 2024 04:55:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7c75d453b719989092e0a53f0c049dc6c247bec0
136585 --> testing pass
Test environment and result as below:
+--------------------------+----------------+
| Environment | dpdk_unit_test |
+==========================+================+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------+----------------+
| Fedora 38 (ARM) | PASS |
+--------------------------+----------------+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------+----------------+
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29112/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-11 7:03 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 7:03 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-11 10:14 dpdklab
2024-02-11 10:04 dpdklab
2024-02-11 9:46 dpdklab
2024-02-11 9:29 dpdklab
2024-02-11 9:27 dpdklab
2024-02-11 8:15 dpdklab
2024-02-11 8:14 dpdklab
2024-02-11 7:50 dpdklab
2024-02-11 7:45 dpdklab
2024-02-11 7:43 dpdklab
2024-02-11 7:41 dpdklab
2024-02-11 7:37 dpdklab
2024-02-11 7:33 dpdklab
2024-02-11 7:33 dpdklab
2024-02-11 7:30 dpdklab
2024-02-11 7:30 dpdklab
2024-02-11 7:30 dpdklab
2024-02-11 7:30 dpdklab
2024-02-11 7:28 dpdklab
2024-02-11 7:26 dpdklab
2024-02-11 7:26 dpdklab
2024-02-11 7:26 dpdklab
2024-02-11 7:23 dpdklab
2024-02-11 7:23 dpdklab
2024-02-11 7:22 dpdklab
2024-02-11 7:20 dpdklab
2024-02-11 7:19 dpdklab
2024-02-11 7:19 dpdklab
2024-02-11 7:18 dpdklab
2024-02-11 7:18 dpdklab
2024-02-11 7:18 dpdklab
2024-02-11 7:17 dpdklab
2024-02-11 7:16 dpdklab
2024-02-11 7:15 dpdklab
2024-02-11 7:15 dpdklab
2024-02-11 7:14 dpdklab
2024-02-11 7:14 dpdklab
2024-02-11 7:13 dpdklab
2024-02-11 7:11 dpdklab
2024-02-11 7:10 dpdklab
2024-02-11 7:07 dpdklab
2024-02-11 7:07 dpdklab
2024-02-11 7:05 dpdklab
2024-02-11 7:05 dpdklab
2024-02-11 7:04 dpdklab
2024-02-11 7:03 dpdklab
2024-02-11 7:00 dpdklab
2024-02-11 6:58 dpdklab
2024-02-11 6:57 dpdklab
2024-02-11 6:57 dpdklab
2024-02-11 6:55 dpdklab
2024-02-11 6:55 dpdklab
2024-02-11 6:54 dpdklab
2024-02-11 6:54 dpdklab
2024-02-11 6:53 dpdklab
2024-02-11 6:53 dpdklab
2024-02-11 6:52 dpdklab
2024-02-11 6:51 dpdklab
2024-02-11 6:50 dpdklab
2024-02-11 6:50 dpdklab
2024-02-11 6:50 dpdklab
2024-02-11 6:49 dpdklab
2024-02-11 6:40 dpdklab
2024-02-11 6:38 dpdklab
2024-02-11 6:37 dpdklab
2024-02-11 6:31 dpdklab
2024-02-11 6:28 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=65c8714f.250a0220.8bb7f.0109SMTPIN_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).