From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137171 [PATCH] [v1] app/testpmd : return if no packets i
Date: Sat, 24 Feb 2024 23:01:24 -0800 (PST) [thread overview]
Message-ID: <65dae5c4.050a0220.7657.00c7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137171
_Testing PASS_
Submitter: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Date: Sunday, February 25 2024 06:16:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8c261a499faa28088489a141238f918be00807bb
137171 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| Debian Buster | PASS |
+-----------------+----------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29251/
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-25 7:01 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 7:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-25 10:12 dpdklab
2024-02-25 9:44 dpdklab
2024-02-25 9:24 dpdklab
2024-02-25 8:12 dpdklab
2024-02-25 7:25 dpdklab
2024-02-25 7:21 dpdklab
2024-02-25 7:20 dpdklab
2024-02-25 7:16 dpdklab
2024-02-25 7:16 dpdklab
2024-02-25 7:15 dpdklab
2024-02-25 7:14 dpdklab
2024-02-25 7:12 dpdklab
2024-02-25 7:09 dpdklab
2024-02-25 7:08 dpdklab
2024-02-25 7:08 dpdklab
2024-02-25 7:08 dpdklab
2024-02-25 7:06 dpdklab
2024-02-25 7:06 dpdklab
2024-02-25 7:06 dpdklab
2024-02-25 7:05 dpdklab
2024-02-25 7:04 dpdklab
2024-02-25 7:04 dpdklab
2024-02-25 7:04 dpdklab
2024-02-25 7:03 dpdklab
2024-02-25 7:03 dpdklab
2024-02-25 7:02 dpdklab
2024-02-25 7:02 dpdklab
2024-02-25 7:02 dpdklab
2024-02-25 7:02 dpdklab
2024-02-25 7:01 dpdklab
2024-02-25 7:01 dpdklab
2024-02-25 7:01 dpdklab
2024-02-25 7:01 dpdklab
2024-02-25 6:59 dpdklab
2024-02-25 6:59 dpdklab
2024-02-25 6:59 dpdklab
2024-02-25 6:58 dpdklab
2024-02-25 6:58 dpdklab
2024-02-25 6:57 dpdklab
2024-02-25 6:57 dpdklab
2024-02-25 6:57 dpdklab
2024-02-25 6:57 dpdklab
2024-02-25 6:56 dpdklab
2024-02-25 6:56 dpdklab
2024-02-25 6:56 dpdklab
2024-02-25 6:55 dpdklab
2024-02-25 6:55 dpdklab
2024-02-25 6:55 dpdklab
2024-02-25 6:55 dpdklab
2024-02-25 6:55 dpdklab
2024-02-25 6:55 dpdklab
2024-02-25 6:54 dpdklab
2024-02-25 6:54 dpdklab
2024-02-25 6:54 dpdklab
2024-02-25 6:54 dpdklab
2024-02-25 6:54 dpdklab
2024-02-25 6:53 dpdklab
2024-02-25 6:53 dpdklab
2024-02-25 6:53 dpdklab
2024-02-25 6:52 dpdklab
2024-02-25 6:52 dpdklab
2024-02-25 6:52 dpdklab
2024-02-25 6:52 dpdklab
2024-02-25 6:51 dpdklab
2024-02-25 6:51 dpdklab
2024-02-25 6:50 dpdklab
2024-02-25 6:50 dpdklab
2024-02-25 6:50 dpdklab
2024-02-25 6:49 dpdklab
2024-02-25 6:49 dpdklab
2024-02-25 6:49 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=65dae5c4.050a0220.7657.00c7SMTPIN_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).