From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147388-147399 [PATCH] [v17,14/14] app/test: add cryptode
Date: Sun, 27 Oct 2024 04:13:01 -0700 (PDT) [thread overview]
Message-ID: <671e203d.170a0220.201bcd.d6beSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241026161502.2348307-13-li.hanxiao@zte.com.cn>
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/147399
_Testing PASS_
Submitter: Hanxiao Li <li.hanxiao@zte.com.cn>
Date: Saturday, October 26 2024 16:14:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3ee7a3e0e0e0f5a81a4b102a834697bc488fb32f
147388-147399 --> testing pass
Upstream job id: Aarch32-Unit-Test#4020
Test environment and result as below:
+-----------------------------+----------------+
| Environment | dpdk_unit_test |
+=============================+================+
| 32-bit Ubuntu 22.04.4 (ARM) | PASS |
+-----------------------------+----------------+
32-bit Ubuntu 22.04.4 (ARM)
Kernel: 5.15.83+ aarch64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31698/
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-10-27 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241026161502.2348307-13-li.hanxiao@zte.com.cn>
2024-10-26 15:55 ` |SUCCESS| pw147388-147399 [PATCH v17 14/14] app/test: add cryptodev test for zsda qemudev
2024-10-26 16:00 ` qemudev
2024-10-26 16:21 ` |SUCCESS| pw147399 " checkpatch
2024-10-26 17:26 ` 0-day Robot
2024-10-27 6:35 ` |SUCCESS| pw147388-147399 [PATCH] [v17,14/14] app/test: add cryptode dpdklab
2024-10-27 6:50 ` dpdklab
2024-10-27 6:53 ` dpdklab
2024-10-27 6:58 ` dpdklab
2024-10-27 7:02 ` dpdklab
2024-10-27 7:08 ` dpdklab
2024-10-27 10:46 ` |PENDING| " dpdklab
2024-10-27 11:13 ` 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=671e203d.170a0220.201bcd.d6beSMTPIN_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).