From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143043-143042 [PATCH] [v9,2/2] examples/l3fwd-power: add
Date: Fri, 09 Aug 2024 08:04:45 -0700 (PDT) [thread overview]
Message-ID: <66b6300d.050a0220.ba0aa.eb7cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240809095012.16717-3-lihuisong@huawei.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/143042
_Testing PASS_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Friday, August 09 2024 09:50:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143043-143042 --> testing pass
Upstream job id: Template-DTS-Pipeline#174126
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/30754/
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-08-09 15:04 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240809095012.16717-3-lihuisong@huawei.com>
2024-08-09 9:35 ` |SUCCESS| pw143043-143042 [PATCH v9 2/2] examples/l3fwd-power: add PM QoS configuration qemudev
2024-08-09 9:40 ` qemudev
2024-08-09 10:00 ` |SUCCESS| pw143042 " checkpatch
2024-08-09 11:02 ` 0-day Robot
2024-08-09 13:56 ` |SUCCESS| pw143043-143042 [PATCH] [v9,2/2] examples/l3fwd-power: add dpdklab
2024-08-09 13:57 ` dpdklab
2024-08-09 13:59 ` dpdklab
2024-08-09 14:04 ` dpdklab
2024-08-09 14:05 ` dpdklab
2024-08-09 14:12 ` dpdklab
2024-08-09 14:17 ` dpdklab
2024-08-09 14:19 ` dpdklab
2024-08-09 14:21 ` |PENDING| " dpdklab
2024-08-09 14:29 ` |SUCCESS| " dpdklab
2024-08-09 14:29 ` dpdklab
2024-08-09 15:04 ` dpdklab
2024-08-09 15:04 ` dpdklab [this message]
2024-08-09 15:59 ` |WARNING| " dpdklab
2024-08-09 16:10 ` |SUCCESS| " dpdklab
2024-08-09 16:11 ` |WARNING| " dpdklab
2024-08-09 16:13 ` dpdklab
2024-08-09 16:15 ` |SUCCESS| " dpdklab
2024-08-09 16:18 ` |WARNING| " dpdklab
2024-08-09 16:19 ` |SUCCESS| " dpdklab
2024-08-09 16:43 ` dpdklab
2024-08-09 20:07 ` |PENDING| " dpdklab
2024-08-09 20:10 ` dpdklab
2024-08-09 20:10 ` dpdklab
2024-08-09 20:17 ` dpdklab
2024-08-09 20:25 ` dpdklab
2024-08-09 21:09 ` dpdklab
2024-08-09 21:18 ` dpdklab
2024-08-09 21:22 ` dpdklab
2024-08-09 21:27 ` dpdklab
2024-08-09 21:29 ` dpdklab
2024-08-09 21:32 ` dpdklab
2024-08-09 21:40 ` dpdklab
2024-08-09 21:43 ` dpdklab
2024-08-09 21:48 ` dpdklab
2024-08-09 21:48 ` dpdklab
2024-08-09 21:53 ` dpdklab
2024-08-09 21:54 ` dpdklab
2024-08-09 21:55 ` dpdklab
2024-08-09 21:56 ` dpdklab
2024-08-09 21:56 ` dpdklab
2024-08-09 21:57 ` dpdklab
2024-08-09 21:58 ` dpdklab
2024-08-09 22:01 ` dpdklab
2024-08-09 22:01 ` dpdklab
2024-08-09 22:03 ` dpdklab
2024-08-09 22:03 ` dpdklab
2024-08-09 22:08 ` dpdklab
2024-08-09 22:09 ` dpdklab
2024-08-09 22:14 ` dpdklab
2024-08-09 22:32 ` dpdklab
2024-08-09 22:33 ` dpdklab
2024-08-09 22:54 ` dpdklab
2024-08-09 22:54 ` dpdklab
2024-08-09 22:54 ` dpdklab
2024-08-09 23:17 ` dpdklab
2024-08-09 23:20 ` dpdklab
2024-08-09 23:57 ` dpdklab
2024-08-10 0:11 ` dpdklab
2024-08-10 0:18 ` dpdklab
2024-08-10 3:30 ` |SUCCESS| " dpdklab
2024-08-10 16:28 ` 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=66b6300d.050a0220.ba0aa.eb7cSMTPIN_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).