From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135944 [PATCH] [v4] gro : packets not getting flushed in
Date: Wed, 17 Jan 2024 22:28:39 -0800 (PST) [thread overview]
Message-ID: <65a8c517.170a0220.bc979.1e3fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135944
_Testing PASS_
Submitter: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Date: Wednesday, January 17 2024 20:24:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39a8b1251b204d3898b4c462184f60bda1b64698
135944 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28893/
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 6:28 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 6:28 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-18 16:02 dpdklab
2024-01-18 8:50 dpdklab
2024-01-18 8:35 dpdklab
2024-01-18 7:44 dpdklab
2024-01-18 7:34 dpdklab
2024-01-18 7:30 dpdklab
2024-01-18 7:07 dpdklab
2024-01-18 7:07 dpdklab
2024-01-18 6:55 dpdklab
2024-01-18 6:52 dpdklab
2024-01-18 6:50 dpdklab
2024-01-18 6:50 dpdklab
2024-01-18 6:50 dpdklab
2024-01-18 6:49 dpdklab
2024-01-18 6:48 dpdklab
2024-01-18 6:47 dpdklab
2024-01-18 6:47 dpdklab
2024-01-18 6:44 dpdklab
2024-01-18 6:41 dpdklab
2024-01-18 6:33 dpdklab
2024-01-18 6:33 dpdklab
2024-01-18 6:31 dpdklab
2024-01-18 6:28 dpdklab
2024-01-18 6:28 dpdklab
2024-01-18 6:28 dpdklab
2024-01-18 6:28 dpdklab
2024-01-18 6:26 dpdklab
2024-01-18 6:24 dpdklab
2024-01-18 6:07 dpdklab
2024-01-18 6:06 dpdklab
2024-01-18 6:00 dpdklab
2024-01-18 5:59 dpdklab
2024-01-18 5:54 dpdklab
2024-01-18 5:52 dpdklab
2024-01-18 5:52 dpdklab
2024-01-18 5:45 dpdklab
2024-01-18 5:44 dpdklab
2024-01-18 5:43 dpdklab
2024-01-18 5:40 dpdklab
2024-01-18 5:20 dpdklab
2024-01-18 5:16 dpdklab
2024-01-18 5:15 dpdklab
2024-01-18 5:14 dpdklab
2024-01-18 5:13 dpdklab
2024-01-18 5:07 dpdklab
2024-01-18 5:07 dpdklab
2024-01-18 5:06 dpdklab
2024-01-18 4:43 dpdklab
2024-01-18 4:41 dpdklab
2024-01-18 4:37 dpdklab
2024-01-18 4:37 dpdklab
2024-01-18 4:37 dpdklab
2024-01-18 4:36 dpdklab
2024-01-18 4:35 dpdklab
2024-01-18 4:35 dpdklab
2024-01-18 4:31 dpdklab
2024-01-18 4:29 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=65a8c517.170a0220.bc979.1e3fSMTPIN_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).