automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw145706-145707 [PATCH] [v1,2/2] app/test: add SM4-XTS tes
Date: Fri, 11 Oct 2024 07:27:39 -0700 (PDT)	[thread overview]
Message-ID: <670935db.050a0220.3d4c7e.9184SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241011011705.1428108-3-li.hanxiao@zte.com.cn>

Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/145707

_Testing PASS_

Submitter: Hanxiao Li <li.hanxiao@zte.com.cn>
Date: Friday, October 11 2024 01:17:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ca37ab343f2e96a92d8828d3e5a1543790d6bc3c

145706-145707 --> testing pass

Upstream job id: Template-DTS-Pipeline#187286

Test environment and result as below:

+--------------+----------------------+
| Environment  | compressdev_zlib_pmd |
+==============+======================+
| Ubuntu 22.04 | PASS                 |
+--------------+----------------------+


Ubuntu 22.04
	Kernel: 5.15.0-100-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31418/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

      parent reply	other threads:[~2024-10-11 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241011011705.1428108-3-li.hanxiao@zte.com.cn>
2024-10-11  0:59 ` |SUCCESS| pw145706-145707 [PATCH v1 2/2] app/test: add SM4-XTS test cases qemudev
2024-10-11  1:03 ` qemudev
2024-10-11  1:21 ` |SUCCESS| pw145707 " checkpatch
2024-10-11  2:23 ` 0-day Robot
2024-10-11 14:24 ` |SUCCESS| pw145706-145707 [PATCH] [v1,2/2] app/test: add SM4-XTS tes dpdklab
2024-10-11 14:27 ` 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=670935db.050a0220.3d4c7e.9184SMTPIN_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).