From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw144265 [PATCH] crypto/scheduler: fix incorrect variable
Date: Wed, 18 Sep 2024 10:27:24 -0700 (PDT) [thread overview]
Message-ID: <66eb0d7c.170a0220.ea315.3f55SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <tencent_24CE9C7896D3134694B645817C0B3A8A5205@qq.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/144265
_Functional Testing PASS_
Submitter: Yong Liang <1269690261@qq.com>
Date: Wednesday, September 18 2024 14:15:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b50d6c67a3c033a49739a0bd1a132aee6d9e324
144265 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#182103
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/31068/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-09-18 17:27 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_24CE9C7896D3134694B645817C0B3A8A5205@qq.com>
2024-09-18 13:49 ` |SUCCESS| pw144265 [PATCH] crypto/scheduler: fix incorrect variable usage qemudev
2024-09-18 13:54 ` qemudev
2024-09-18 14:16 ` checkpatch
2024-09-18 15:04 ` 0-day Robot
2024-09-18 17:11 ` |SUCCESS| pw144265 [PATCH] crypto/scheduler: fix incorrect variable dpdklab
2024-09-18 17:14 ` dpdklab
2024-09-18 17:27 ` dpdklab [this message]
2024-09-18 18:09 ` dpdklab
2024-09-18 18:12 ` dpdklab
2024-09-18 18:21 ` dpdklab
2024-09-18 18:34 ` dpdklab
2024-09-18 18:45 ` dpdklab
2024-09-18 18:48 ` |PENDING| " dpdklab
2024-09-18 18:50 ` dpdklab
2024-09-18 18:53 ` |SUCCESS| " dpdklab
2024-09-18 19:16 ` |PENDING| " dpdklab
2024-09-18 19:26 ` |SUCCESS| " dpdklab
2024-09-18 19:26 ` dpdklab
2024-09-18 19:40 ` dpdklab
2024-09-18 19:42 ` dpdklab
2024-09-18 19:52 ` dpdklab
2024-09-18 20:02 ` |PENDING| " dpdklab
2024-09-18 20:06 ` |SUCCESS| " dpdklab
2024-09-18 20:06 ` dpdklab
2024-09-18 20:07 ` dpdklab
2024-09-18 20:15 ` dpdklab
2024-09-18 20:20 ` dpdklab
2024-09-18 20:32 ` |PENDING| " dpdklab
2024-09-18 20:38 ` |SUCCESS| " dpdklab
2024-09-18 20:38 ` dpdklab
2024-09-18 20:39 ` dpdklab
2024-09-18 20:46 ` dpdklab
2024-09-18 21:16 ` dpdklab
2024-09-18 21:28 ` dpdklab
2024-09-18 21:49 ` |PENDING| " dpdklab
2024-09-18 22:02 ` |SUCCESS| " dpdklab
2024-09-18 22:30 ` dpdklab
2024-09-18 23:02 ` dpdklab
2024-09-18 23:06 ` dpdklab
2024-09-19 4:36 ` dpdklab
2024-09-19 18:16 ` dpdklab
2024-09-20 0:47 ` dpdklab
2024-09-22 16:12 ` dpdklab
2024-09-22 16:23 ` dpdklab
2024-09-22 17:11 ` dpdklab
2024-09-22 17:22 ` 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=66eb0d7c.170a0220.ea315.3f55SMTPIN_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).