From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143051-143053 [PATCH] [v2,3/3] test/alarm: rewrite the a
Date: Fri, 09 Aug 2024 11:33:35 -0700 (PDT) [thread overview]
Message-ID: <66b660ff.050a0220.365bd7.06feSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240809152540.9568-4-stephen@networkplumber.org>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/143053
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, August 09 2024 15:24:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143051-143053 --> testing pass
Upstream job id: Template-DTS-Pipeline#174164
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/30758/
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 18:33 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240809152540.9568-4-stephen@networkplumber.org>
2024-08-09 14:59 ` |SUCCESS| pw143051-143053 [PATCH v2 3/3] test/alarm: rewrite the alarm test qemudev
2024-08-09 15:03 ` qemudev
2024-08-09 15:26 ` |WARNING| pw143053 " checkpatch
2024-08-09 16:42 ` |SUCCESS| " 0-day Robot
2024-08-09 17:52 ` |PENDING| pw143051-143053 [PATCH] [v2,3/3] test/alarm: rewrite the a dpdklab
2024-08-09 17:59 ` |SUCCESS| " dpdklab
2024-08-09 18:00 ` dpdklab
2024-08-09 18:13 ` dpdklab
2024-08-09 18:21 ` dpdklab
2024-08-09 18:33 ` dpdklab [this message]
2024-08-09 19:11 ` dpdklab
2024-08-09 19:31 ` dpdklab
2024-08-09 20:01 ` dpdklab
2024-08-09 20:05 ` dpdklab
2024-08-09 20:22 ` |PENDING| " dpdklab
2024-08-09 21:43 ` dpdklab
2024-08-09 21:44 ` dpdklab
2024-08-09 21:46 ` dpdklab
2024-08-09 21:47 ` |SUCCESS| " dpdklab
2024-08-09 21:49 ` dpdklab
2024-08-09 21:50 ` dpdklab
2024-08-09 21:53 ` dpdklab
2024-08-09 21:53 ` dpdklab
2024-08-09 21:57 ` dpdklab
2024-08-09 21:58 ` |PENDING| " dpdklab
2024-08-09 22:05 ` |SUCCESS| " dpdklab
2024-08-09 22:17 ` |PENDING| " dpdklab
2024-08-09 23:05 ` dpdklab
2024-08-09 23:19 ` dpdklab
2024-08-09 23:20 ` dpdklab
2024-08-09 23:20 ` dpdklab
2024-08-09 23:20 ` dpdklab
2024-08-09 23:20 ` dpdklab
2024-08-09 23:32 ` dpdklab
2024-08-09 23:33 ` dpdklab
2024-08-09 23:34 ` dpdklab
2024-08-09 23:34 ` dpdklab
2024-08-09 23:34 ` dpdklab
2024-08-09 23:35 ` dpdklab
2024-08-09 23:35 ` dpdklab
2024-08-09 23:36 ` dpdklab
2024-08-09 23:36 ` dpdklab
2024-08-09 23:36 ` dpdklab
2024-08-09 23:36 ` dpdklab
2024-08-09 23:36 ` dpdklab
2024-08-09 23:37 ` dpdklab
2024-08-09 23:37 ` dpdklab
2024-08-09 23:37 ` dpdklab
2024-08-09 23:38 ` dpdklab
2024-08-09 23:39 ` dpdklab
2024-08-09 23:39 ` dpdklab
2024-08-09 23:44 ` dpdklab
2024-08-09 23:52 ` dpdklab
2024-08-09 23:53 ` dpdklab
2024-08-09 23:54 ` dpdklab
2024-08-09 23:59 ` dpdklab
2024-08-10 0:03 ` dpdklab
2024-08-10 0:05 ` dpdklab
2024-08-10 0:06 ` dpdklab
2024-08-10 0:07 ` dpdklab
2024-08-10 0:08 ` dpdklab
2024-08-10 0:10 ` dpdklab
2024-08-10 0:11 ` dpdklab
2024-08-10 0:13 ` dpdklab
2024-08-10 0:14 ` |SUCCESS| " dpdklab
2024-08-10 0:19 ` |PENDING| " dpdklab
2024-08-10 0:27 ` dpdklab
2024-08-10 0:48 ` dpdklab
2024-08-10 0:55 ` dpdklab
2024-08-10 4:29 ` |SUCCESS| " dpdklab
2024-08-10 16:48 ` |PENDING| " 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=66b660ff.050a0220.365bd7.06feSMTPIN_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).