From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Kumara Parameshwaran <kumaraparamesh92@gmail.com>,
dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136842 [PATCH] [v8] app/testpmd : fix packets not gettin
Date: Fri, 16 Feb 2024 03:25:10 -0800 (PST) [thread overview]
Message-ID: <65cf4616.050a0220.3d94f.41d0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136842
_Testing PASS_
Submitter: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Date: Friday, February 16 2024 03:47:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31d9d436f263a3f4313ad4c029a9905d6be6cbd6
136842 --> testing pass
Test environment and result as below:
+--------------------------+---------------------------+----------------+------------------------------+
| Environment | cryptodev_sw_zuc_autotest | dpdk_unit_test | cryptodev_sw_snow3g_autotest |
+==========================+===========================+================+==============================+
| Debian 11 (arm) | PASS | SKIPPED | PASS |
+--------------------------+---------------------------+----------------+------------------------------+
| Debian 11 (Buster) (ARM) | SKIPPED | PASS | SKIPPED |
+--------------------------+---------------------------+----------------+------------------------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.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/29168/
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-16 11:25 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 11:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 16:13 dpdklab
2024-02-16 16:06 dpdklab
2024-02-16 12:37 dpdklab
2024-02-16 12:37 dpdklab
2024-02-16 12:28 dpdklab
2024-02-16 12:08 dpdklab
2024-02-16 12:01 dpdklab
2024-02-16 12:00 dpdklab
2024-02-16 11:59 dpdklab
2024-02-16 11:51 dpdklab
2024-02-16 11:47 dpdklab
2024-02-16 11:46 dpdklab
2024-02-16 11:45 dpdklab
2024-02-16 11:45 dpdklab
2024-02-16 11:45 dpdklab
2024-02-16 11:45 dpdklab
2024-02-16 11:45 dpdklab
2024-02-16 11:41 dpdklab
2024-02-16 11:40 dpdklab
2024-02-16 11:39 dpdklab
2024-02-16 11:37 dpdklab
2024-02-16 11:36 dpdklab
2024-02-16 11:36 dpdklab
2024-02-16 11:36 dpdklab
2024-02-16 11:36 dpdklab
2024-02-16 11:36 dpdklab
2024-02-16 11:35 dpdklab
2024-02-16 11:34 dpdklab
2024-02-16 11:34 dpdklab
2024-02-16 11:34 dpdklab
2024-02-16 11:33 dpdklab
2024-02-16 11:32 dpdklab
2024-02-16 11:30 dpdklab
2024-02-16 11:30 dpdklab
2024-02-16 11:29 dpdklab
2024-02-16 11:28 dpdklab
2024-02-16 11:27 dpdklab
2024-02-16 11:25 dpdklab
2024-02-16 11:25 dpdklab
2024-02-16 11:25 dpdklab
2024-02-16 11:21 dpdklab
2024-02-16 11:21 dpdklab
2024-02-16 11:21 dpdklab
2024-02-16 11:20 dpdklab
2024-02-16 11:19 dpdklab
2024-02-16 11:18 dpdklab
2024-02-16 11:18 dpdklab
2024-02-16 11:16 dpdklab
2024-02-16 11:16 dpdklab
2024-02-16 11:15 dpdklab
2024-02-16 11:14 dpdklab
2024-02-16 11:11 dpdklab
2024-02-16 11:11 dpdklab
2024-02-16 11:10 dpdklab
2024-02-16 11:10 dpdklab
2024-02-16 11:09 dpdklab
2024-02-16 11:09 dpdklab
2024-02-16 11:08 dpdklab
2024-02-16 11:08 dpdklab
2024-02-16 11:08 dpdklab
2024-02-16 11:07 dpdklab
2024-02-16 11:07 dpdklab
2024-02-16 11:07 dpdklab
2024-02-16 11:06 dpdklab
2024-02-16 11:05 dpdklab
2024-02-16 11:04 dpdklab
2024-02-16 11:04 dpdklab
2024-02-16 11:04 dpdklab
2024-02-16 10:58 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=65cf4616.050a0220.3d94f.41d0SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=kumaraparamesh92@gmail.com \
--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).