From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw145844 [PATCH] [v3] hash: separate param checks in hash
Date: Mon, 14 Oct 2024 19:43:30 -0700 (PDT) [thread overview]
Message-ID: <670dd6d2.050a0220.f298.0b97SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241014101916.2043948-1-niall.meade@intel.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/145844
_Testing PASS_
Submitter: Niall Meade <niall.meade@intel.com>
Date: Monday, October 14 2024 10:19:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5f7b98189de733080656989d63b0e7ffd249830a
145844 --> testing pass
Upstream job id: Template-DTS-Pipeline#188038
Test environment and result as below:
+--------------------+----------------------+
| Environment | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS |
+--------------------+----------------------+
| Ubuntu 22.04 | PASS |
+--------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
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/31464/
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-15 2:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241014101916.2043948-1-niall.meade@intel.com>
2024-10-14 10:19 ` |SUCCESS| pw145844 [PATCH v3] hash: separate param checks in hash create func qemudev
2024-10-14 10:21 ` checkpatch
2024-10-14 10:23 ` qemudev
2024-10-14 12:02 ` 0-day Robot
2024-10-15 0:26 ` |SUCCESS| pw145844 [PATCH] [v3] hash: separate param checks in hash dpdklab
2024-10-15 0:51 ` dpdklab
2024-10-15 1:28 ` dpdklab
2024-10-15 2:43 ` 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=670dd6d2.050a0220.f298.0b97SMTPIN_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).