From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Jerin Jacob <jerinj@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 9985c7bc4b1f3ddb027951d419a5154c65b2a416
Date: Wed, 26 Jun 2024 14:45:53 -0700 (PDT) [thread overview]
Message-ID: <667c8c11.050a0220.ea1bd.6395SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-eventdev
9985c7bc4b1f3ddb027951d419a5154c65b2a416 --> testing pass
Test environment and result as below:
+-----------------------------+----------------+
| Environment | dpdk_unit_test |
+=============================+================+
| 32-bit Ubuntu 20.04.4 (ARM) | PASS |
+-----------------------------+----------------+
| CentOS Stream 9 (ARM) | PASS |
+-----------------------------+----------------+
32-bit Ubuntu 20.04.4 (ARM)
Kernel: 5.4.0-155-generic aarch64
Compiler: gcc 9.4
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29599/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-06-26 21:45 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 21:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-27 23:02 dpdklab
2024-06-27 10:19 dpdklab
2024-06-27 10:01 dpdklab
2024-06-27 1:11 dpdklab
2024-06-27 0:55 dpdklab
2024-06-27 0:10 dpdklab
2024-06-27 0:01 dpdklab
2024-06-26 23:49 dpdklab
2024-06-26 23:45 dpdklab
2024-06-26 23:41 dpdklab
2024-06-26 23:41 dpdklab
2024-06-26 23:33 dpdklab
2024-06-26 23:28 dpdklab
2024-06-26 23:25 dpdklab
2024-06-26 23:24 dpdklab
2024-06-26 23:23 dpdklab
2024-06-26 23:23 dpdklab
2024-06-26 23:21 dpdklab
2024-06-26 23:18 dpdklab
2024-06-26 23:16 dpdklab
2024-06-26 23:15 dpdklab
2024-06-26 23:14 dpdklab
2024-06-26 23:10 dpdklab
2024-06-26 23:09 dpdklab
2024-06-26 23:09 dpdklab
2024-06-26 23:08 dpdklab
2024-06-26 23:08 dpdklab
2024-06-26 23:06 dpdklab
2024-06-26 23:01 dpdklab
2024-06-26 22:56 dpdklab
2024-06-26 22:56 dpdklab
2024-06-26 22:56 dpdklab
2024-06-26 22:55 dpdklab
2024-06-26 22:50 dpdklab
2024-06-26 22:48 dpdklab
2024-06-26 22:42 dpdklab
2024-06-26 22:40 dpdklab
2024-06-26 22:39 dpdklab
2024-06-26 22:37 dpdklab
2024-06-26 22:33 dpdklab
2024-06-26 22:32 dpdklab
2024-06-26 22:25 dpdklab
2024-06-26 22:25 dpdklab
2024-06-26 22:16 dpdklab
2024-06-26 22:15 dpdklab
2024-06-26 22:09 dpdklab
2024-06-26 22:07 dpdklab
2024-06-26 22:03 dpdklab
2024-06-26 22:02 dpdklab
2024-06-26 22:02 dpdklab
2024-06-26 22:02 dpdklab
2024-06-26 22:01 dpdklab
2024-06-26 22:01 dpdklab
2024-06-26 21:59 dpdklab
2024-06-26 21:59 dpdklab
2024-06-26 21:59 dpdklab
2024-06-26 21:57 dpdklab
2024-06-26 21:55 dpdklab
2024-06-26 21:53 dpdklab
2024-06-26 21:50 dpdklab
2024-06-26 21:47 dpdklab
2024-06-26 21:46 dpdklab
2024-06-26 21:39 dpdklab
2024-06-26 21:38 dpdklab
2024-06-26 21:35 dpdklab
2024-06-26 21:34 dpdklab
2024-06-26 21:33 dpdklab
2024-06-26 21:30 dpdklab
2024-06-26 21:30 dpdklab
2024-06-26 21:29 dpdklab
2024-06-26 21:23 dpdklab
2024-06-26 21:12 dpdklab
2024-06-26 21:11 dpdklab
2024-06-26 21:08 dpdklab
2024-06-26 21:07 dpdklab
2024-06-26 21:03 dpdklab
2024-06-26 21:03 dpdklab
2024-06-26 19:29 dpdklab
2024-06-26 19:13 dpdklab
2024-06-26 19:05 dpdklab
2024-06-26 19:04 dpdklab
2024-06-26 18:56 dpdklab
2024-06-26 18:56 dpdklab
2024-06-26 18:53 dpdklab
2024-06-26 18:49 dpdklab
2024-06-26 18:44 dpdklab
2024-06-26 18:43 dpdklab
2024-06-26 18:40 dpdklab
2024-06-26 18:35 dpdklab
2024-06-26 18:20 dpdklab
2024-06-26 18:10 dpdklab
2024-06-26 18:08 dpdklab
2024-06-26 17:57 dpdklab
2024-06-26 17:40 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=667c8c11.050a0220.ea1bd.6395SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=jerinj@marvell.com \
--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).