From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147704-147706 [PATCH] [RFC,v3,3/3] examples: add lcore t
Date: Wed, 30 Oct 2024 05:57:22 -0700 (PDT) [thread overview]
Message-ID: <67222d32.050a0220.2bf7c2.808dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241030054133.520-4-vipin.varghese@amd.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/147706
_Testing PASS_
Submitter: Varghese, Vipin <vipin.varghese@amd.com>
Date: Wednesday, October 30 2024 05:41:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6dad0bb5c8621644beca86ff5f4910a943ba604d
147704-147706 --> testing pass
Upstream job id: Template-DTS-Pipeline#192786
Test environment and result as below:
+--------------------+----------------------+
| Environment | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS |
+--------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-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/31762/
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-10-30 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241030054133.520-4-vipin.varghese@amd.com>
2024-10-30 5:15 ` |SUCCESS| pw147704-147706 [RFC v3 3/3] examples: add lcore topology API calls qemudev
2024-10-30 5:19 ` |FAILURE| " qemudev
2024-10-30 5:48 ` |SUCCESS| pw147706 " checkpatch
2024-10-30 8:44 ` |FAILURE| " 0-day Robot
2024-10-30 12:57 ` dpdklab [this message]
2024-10-30 15:56 ` |SUCCESS| pw147704-147706 [PATCH] [RFC,v3,3/3] examples: add lcore t dpdklab
2024-10-30 16:11 ` dpdklab
2024-10-30 16:59 ` 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=67222d32.050a0220.2bf7c2.808dSMTPIN_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).