From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
Date: Fri, 15 Dec 2023 18:02:35 -0800 (PST) [thread overview]
Message-ID: <657d053b.0d0a0220.32208.9041SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
e5dc404d33ac1c6cea5c62a88489746c5cb5e35e --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27369/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-16 2:02 UTC|newest]
Thread overview: 203+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 2:02 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-20 3:18 dpdklab
2023-12-20 2:33 dpdklab
2023-12-20 2:31 dpdklab
2023-12-20 2:25 dpdklab
2023-12-20 2:25 dpdklab
2023-12-20 2:24 dpdklab
2023-12-20 2:24 dpdklab
2023-12-20 2:19 dpdklab
2023-12-20 2:19 dpdklab
2023-12-20 2:18 dpdklab
2023-12-20 2:17 dpdklab
2023-12-20 2:17 dpdklab
2023-12-20 2:17 dpdklab
2023-12-20 2:16 dpdklab
2023-12-20 2:15 dpdklab
2023-12-20 2:14 dpdklab
2023-12-20 2:14 dpdklab
2023-12-20 2:13 dpdklab
2023-12-20 2:13 dpdklab
2023-12-20 2:12 dpdklab
2023-12-20 2:12 dpdklab
2023-12-20 2:12 dpdklab
2023-12-20 2:10 dpdklab
2023-12-20 2:08 dpdklab
2023-12-20 2:08 dpdklab
2023-12-20 2:07 dpdklab
2023-12-20 2:07 dpdklab
2023-12-20 2:07 dpdklab
2023-12-20 2:06 dpdklab
2023-12-20 2:05 dpdklab
2023-12-20 2:05 dpdklab
2023-12-20 2:05 dpdklab
2023-12-20 2:04 dpdklab
2023-12-20 2:04 dpdklab
2023-12-20 2:03 dpdklab
2023-12-20 2:03 dpdklab
2023-12-20 2:02 dpdklab
2023-12-20 2:02 dpdklab
2023-12-20 2:02 dpdklab
2023-12-20 2:02 dpdklab
2023-12-20 2:02 dpdklab
2023-12-20 2:02 dpdklab
2023-12-20 2:01 dpdklab
2023-12-20 2:01 dpdklab
2023-12-20 2:01 dpdklab
2023-12-20 2:01 dpdklab
2023-12-20 2:00 dpdklab
2023-12-20 2:00 dpdklab
2023-12-20 2:00 dpdklab
2023-12-20 2:00 dpdklab
2023-12-20 1:59 dpdklab
2023-12-20 1:59 dpdklab
2023-12-20 1:59 dpdklab
2023-12-20 1:59 dpdklab
2023-12-18 3:21 dpdklab
2023-12-18 2:46 dpdklab
2023-12-18 2:36 dpdklab
2023-12-18 2:32 dpdklab
2023-12-18 2:28 dpdklab
2023-12-18 2:26 dpdklab
2023-12-18 2:25 dpdklab
2023-12-18 2:23 dpdklab
2023-12-18 2:22 dpdklab
2023-12-18 2:21 dpdklab
2023-12-18 2:20 dpdklab
2023-12-18 2:19 dpdklab
2023-12-18 2:19 dpdklab
2023-12-18 2:17 dpdklab
2023-12-18 2:16 dpdklab
2023-12-18 2:15 dpdklab
2023-12-18 2:15 dpdklab
2023-12-18 2:14 dpdklab
2023-12-18 2:14 dpdklab
2023-12-18 2:13 dpdklab
2023-12-18 2:13 dpdklab
2023-12-18 2:13 dpdklab
2023-12-18 2:12 dpdklab
2023-12-18 2:12 dpdklab
2023-12-18 2:11 dpdklab
2023-12-18 2:10 dpdklab
2023-12-18 2:10 dpdklab
2023-12-18 2:09 dpdklab
2023-12-18 2:09 dpdklab
2023-12-18 2:09 dpdklab
2023-12-18 2:08 dpdklab
2023-12-18 2:08 dpdklab
2023-12-18 2:07 dpdklab
2023-12-18 2:07 dpdklab
2023-12-18 2:06 dpdklab
2023-12-18 2:06 dpdklab
2023-12-18 2:06 dpdklab
2023-12-18 2:05 dpdklab
2023-12-18 2:05 dpdklab
2023-12-18 2:03 dpdklab
2023-12-18 2:02 dpdklab
2023-12-16 4:54 dpdklab
2023-12-16 2:31 dpdklab
2023-12-16 2:29 dpdklab
2023-12-16 2:29 dpdklab
2023-12-16 2:23 dpdklab
2023-12-16 2:22 dpdklab
2023-12-16 2:19 dpdklab
2023-12-16 2:18 dpdklab
2023-12-16 2:18 dpdklab
2023-12-16 2:17 dpdklab
2023-12-16 2:16 dpdklab
2023-12-16 2:16 dpdklab
2023-12-16 2:15 dpdklab
2023-12-16 2:14 dpdklab
2023-12-16 2:14 dpdklab
2023-12-16 2:13 dpdklab
2023-12-16 2:13 dpdklab
2023-12-16 2:13 dpdklab
2023-12-16 2:13 dpdklab
2023-12-16 2:12 dpdklab
2023-12-16 2:11 dpdklab
2023-12-16 2:11 dpdklab
2023-12-16 2:11 dpdklab
2023-12-16 2:10 dpdklab
2023-12-16 2:09 dpdklab
2023-12-16 2:08 dpdklab
2023-12-16 2:08 dpdklab
2023-12-16 2:08 dpdklab
2023-12-16 2:08 dpdklab
2023-12-16 2:08 dpdklab
2023-12-16 2:06 dpdklab
2023-12-16 2:06 dpdklab
2023-12-16 2:06 dpdklab
2023-12-16 2:05 dpdklab
2023-12-16 2:04 dpdklab
2023-12-16 2:03 dpdklab
2023-12-16 2:03 dpdklab
2023-12-16 2:03 dpdklab
2023-12-16 2:03 dpdklab
2023-12-16 2:03 dpdklab
2023-12-16 2:02 dpdklab
2023-12-16 2:02 dpdklab
2023-12-16 2:02 dpdklab
2023-12-16 2:01 dpdklab
2023-12-16 2:01 dpdklab
2023-12-16 2:01 dpdklab
2023-12-16 2:01 dpdklab
2023-12-16 2:00 dpdklab
2023-12-16 2:00 dpdklab
2023-12-16 2:00 dpdklab
2023-12-16 2:00 dpdklab
2023-12-16 1:59 dpdklab
2023-12-16 1:59 dpdklab
2023-12-16 1:59 dpdklab
2023-12-14 3:21 dpdklab
2023-12-14 2:35 dpdklab
2023-12-14 2:33 dpdklab
2023-12-14 2:32 dpdklab
2023-12-14 2:25 dpdklab
2023-12-14 2:20 dpdklab
2023-12-14 2:18 dpdklab
2023-12-14 2:18 dpdklab
2023-12-14 2:18 dpdklab
2023-12-14 2:17 dpdklab
2023-12-14 2:17 dpdklab
2023-12-14 2:16 dpdklab
2023-12-14 2:16 dpdklab
2023-12-14 2:16 dpdklab
2023-12-14 2:15 dpdklab
2023-12-14 2:15 dpdklab
2023-12-14 2:14 dpdklab
2023-12-14 2:14 dpdklab
2023-12-14 2:13 dpdklab
2023-12-14 2:13 dpdklab
2023-12-14 2:13 dpdklab
2023-12-14 2:11 dpdklab
2023-12-14 2:11 dpdklab
2023-12-14 2:10 dpdklab
2023-12-14 2:10 dpdklab
2023-12-14 2:10 dpdklab
2023-12-14 2:09 dpdklab
2023-12-14 2:09 dpdklab
2023-12-14 2:09 dpdklab
2023-12-14 2:08 dpdklab
2023-12-14 2:08 dpdklab
2023-12-14 2:07 dpdklab
2023-12-14 2:07 dpdklab
2023-12-14 2:06 dpdklab
2023-12-14 2:06 dpdklab
2023-12-14 2:05 dpdklab
2023-12-14 2:05 dpdklab
2023-12-14 2:04 dpdklab
2023-12-14 2:04 dpdklab
2023-12-14 2:03 dpdklab
2023-12-14 2:03 dpdklab
2023-12-14 2:03 dpdklab
2023-12-14 2:03 dpdklab
2023-12-14 2:02 dpdklab
2023-12-14 2:02 dpdklab
2023-12-14 2:02 dpdklab
2023-12-14 2:02 dpdklab
2023-12-14 2:01 dpdklab
2023-12-14 2:01 dpdklab
2023-12-14 2:01 dpdklab
2023-12-14 2:01 dpdklab
2023-12-14 2:00 dpdklab
2023-12-14 2:00 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=657d053b.0d0a0220.32208.9041SMTPIN_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).