From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw145931-145948 [PATCH] [v1,18/18] doc/guides/nics: add do
Date: Tue, 15 Oct 2024 03:33:03 -0700 (PDT) [thread overview]
Message-ID: <670e44df.020a0220.1a0017.2bf5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241015030928.70642-19-howard_wang@realsil.com.cn>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/145948
_Testing PASS_
Submitter: Howard Wang <howard_wang@realsil.com.cn>
Date: Tuesday, October 15 2024 03:09:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2e424aeb6edf8c4990abf266aaa8814a8050616
145931-145948 --> testing pass
Upstream job id: Template-DTS-Pipeline#188407
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/31484/
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 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241015030928.70642-19-howard_wang@realsil.com.cn>
2024-10-15 2:45 ` |SUCCESS| pw145931-145948 [PATCH v1 18/18] doc/guides/nics: add documents for r8169 pmd qemudev
2024-10-15 2:50 ` qemudev
2024-10-15 3:13 ` |WARNING| pw145948 " checkpatch
2024-10-15 5:42 ` |FAILURE| " 0-day Robot
2024-10-15 9:28 ` |SUCCESS| pw145931-145948 [PATCH] [v1,18/18] doc/guides/nics: add do dpdklab
2024-10-15 10:33 ` 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=670e44df.020a0220.1a0017.2bf5SMTPIN_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).