From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw144359-144364 [PATCH] [v3,6/6] app/crypto-perf: support
Date: Mon, 23 Sep 2024 07:07:49 -0700 (PDT) [thread overview]
Message-ID: <66f17635.0c0a0220.15ddff.a3b6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240920130950.1297-6-gmuthukrishn@marvell.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/144364
_Functional Testing PASS_
Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Friday, September 20 2024 13:09:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b50d6c67a3c033a49739a0bd1a132aee6d9e324
144359-144364 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#182677
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| cmdline | PASS |
+-----------------+--------+
| ipv4_reassembly | PASS |
+-----------------+--------+
| l2fwd | PASS |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31100/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-09-23 14:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240920130950.1297-6-gmuthukrishn@marvell.com>
2024-09-20 12:44 ` |SUCCESS| pw144359-144364 [PATCH v3 6/6] app/crypto-perf: support EDDSA qemudev
2024-09-20 12:49 ` qemudev
2024-09-20 13:11 ` |SUCCESS| pw144364 " checkpatch
2024-09-20 14:04 ` |FAILURE| " 0-day Robot
2024-09-20 16:51 ` |SUCCESS| pw144359-144364 [PATCH] [v3,6/6] app/crypto-perf: support dpdklab
2024-09-20 16:59 ` dpdklab
2024-09-20 17:03 ` dpdklab
2024-09-20 17:10 ` dpdklab
2024-09-20 18:04 ` |PENDING| " dpdklab
2024-09-20 18:20 ` |SUCCESS| " dpdklab
2024-09-20 18:23 ` |PENDING| " dpdklab
2024-09-20 18:30 ` |FAILURE| " dpdklab
2024-09-20 18:30 ` dpdklab
2024-09-20 18:31 ` |SUCCESS| " dpdklab
2024-09-20 18:32 ` dpdklab
2024-09-20 18:35 ` |FAILURE| " dpdklab
2024-09-20 18:40 ` dpdklab
2024-09-20 18:41 ` |PENDING| " dpdklab
2024-09-20 18:49 ` |FAILURE| " dpdklab
2024-09-20 18:51 ` |SUCCESS| " dpdklab
2024-09-20 18:52 ` |FAILURE| " dpdklab
2024-09-20 18:55 ` dpdklab
2024-09-20 18:58 ` dpdklab
2024-09-20 18:59 ` dpdklab
2024-09-20 19:12 ` |PENDING| " dpdklab
2024-09-20 19:12 ` |FAILURE| " dpdklab
2024-09-20 19:22 ` |PENDING| " dpdklab
2024-09-20 19:25 ` |SUCCESS| " dpdklab
2024-09-20 19:44 ` |FAILURE| " dpdklab
2024-09-20 20:02 ` |SUCCESS| " dpdklab
2024-09-20 20:09 ` |FAILURE| " dpdklab
2024-09-20 20:15 ` dpdklab
2024-09-20 20:17 ` dpdklab
2024-09-20 20:29 ` |PENDING| " dpdklab
2024-09-20 21:21 ` |FAILURE| " dpdklab
2024-09-20 21:22 ` |SUCCESS| " dpdklab
2024-09-20 22:18 ` dpdklab
2024-09-20 23:14 ` dpdklab
2024-09-21 14:16 ` dpdklab
2024-09-21 14:51 ` dpdklab
2024-09-23 11:13 ` dpdklab
2024-09-23 11:54 ` dpdklab
2024-09-23 13:03 ` dpdklab
2024-09-23 14:07 ` dpdklab [this message]
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=66f17635.0c0a0220.15ddff.a3b6SMTPIN_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).