From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 6e999364a6afb9189029154b1ac55b4ad5fb9b3f
Date: Sun, 01 Oct 2023 18:43:27 -0700 (PDT) [thread overview]
Message-ID: <651a203f.0c0a0220.475ce.4b46SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
6e999364a6afb9189029154b1ac55b4ad5fb9b3f --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Arch Linux | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26320/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-02 1:43 UTC|newest]
Thread overview: 142+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 1:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-02 2:25 dpdklab
2023-10-02 2:23 dpdklab
2023-10-02 2:22 dpdklab
2023-10-02 2:19 dpdklab
2023-10-02 2:12 dpdklab
2023-10-02 2:07 dpdklab
2023-10-02 2:05 dpdklab
2023-10-02 2:04 dpdklab
2023-10-02 2:00 dpdklab
2023-10-02 1:57 dpdklab
2023-10-02 1:52 dpdklab
2023-10-02 1:49 dpdklab
2023-10-02 1:48 dpdklab
2023-10-02 1:39 dpdklab
2023-10-02 1:38 dpdklab
2023-10-02 1:38 dpdklab
2023-10-02 1:37 dpdklab
2023-10-02 1:37 dpdklab
2023-10-02 1:37 dpdklab
2023-10-02 1:35 dpdklab
2023-10-02 1:22 dpdklab
2023-10-02 1:21 dpdklab
2023-10-02 1:20 dpdklab
2023-10-02 1:19 dpdklab
2023-10-02 1:18 dpdklab
2023-10-02 1:18 dpdklab
2023-10-02 1:17 dpdklab
2023-10-02 1:15 dpdklab
2023-10-02 1:15 dpdklab
2023-10-02 1:14 dpdklab
2023-10-02 1:12 dpdklab
2023-10-02 1:12 dpdklab
2023-10-02 1:11 dpdklab
2023-10-02 1:07 dpdklab
2023-10-02 1:05 dpdklab
2023-10-02 1:04 dpdklab
2023-10-02 1:03 dpdklab
2023-10-02 1:03 dpdklab
2023-10-02 1:03 dpdklab
2023-10-02 1:02 dpdklab
2023-10-02 1:02 dpdklab
2023-10-02 1:01 dpdklab
2023-10-02 1:00 dpdklab
2023-10-02 0:59 dpdklab
2023-10-02 0:56 dpdklab
2023-10-02 0:56 dpdklab
2023-10-02 0:56 dpdklab
2023-10-02 0:56 dpdklab
2023-10-01 2:50 dpdklab
2023-10-01 2:35 dpdklab
2023-10-01 2:35 dpdklab
2023-10-01 2:35 dpdklab
2023-10-01 2:24 dpdklab
2023-10-01 2:20 dpdklab
2023-10-01 2:19 dpdklab
2023-10-01 2:15 dpdklab
2023-10-01 2:13 dpdklab
2023-10-01 2:08 dpdklab
2023-10-01 2:07 dpdklab
2023-10-01 2:00 dpdklab
2023-10-01 1:56 dpdklab
2023-10-01 1:54 dpdklab
2023-10-01 1:45 dpdklab
2023-10-01 1:45 dpdklab
2023-10-01 1:39 dpdklab
2023-10-01 1:38 dpdklab
2023-10-01 1:36 dpdklab
2023-10-01 1:31 dpdklab
2023-10-01 1:27 dpdklab
2023-10-01 1:22 dpdklab
2023-10-01 1:22 dpdklab
2023-10-01 1:22 dpdklab
2023-10-01 1:21 dpdklab
2023-10-01 1:18 dpdklab
2023-10-01 1:17 dpdklab
2023-10-01 1:17 dpdklab
2023-10-01 1:14 dpdklab
2023-10-01 1:13 dpdklab
2023-10-01 1:12 dpdklab
2023-10-01 1:12 dpdklab
2023-10-01 1:08 dpdklab
2023-10-01 1:08 dpdklab
2023-10-01 1:08 dpdklab
2023-10-01 1:08 dpdklab
2023-10-01 1:08 dpdklab
2023-10-01 1:07 dpdklab
2023-10-01 1:07 dpdklab
2023-10-01 1:07 dpdklab
2023-10-01 1:07 dpdklab
2023-10-01 1:06 dpdklab
2023-10-01 1:06 dpdklab
2023-10-01 1:06 dpdklab
2023-10-01 1:06 dpdklab
2023-10-01 1:05 dpdklab
2023-10-01 1:05 dpdklab
2023-09-30 2:59 dpdklab
2023-09-30 2:59 dpdklab
2023-09-30 2:39 dpdklab
2023-09-30 2:09 dpdklab
2023-09-30 2:07 dpdklab
2023-09-30 2:05 dpdklab
2023-09-30 2:03 dpdklab
2023-09-30 2:01 dpdklab
2023-09-30 1:58 dpdklab
2023-09-30 1:57 dpdklab
2023-09-30 1:56 dpdklab
2023-09-30 1:33 dpdklab
2023-09-30 1:32 dpdklab
2023-09-30 1:26 dpdklab
2023-09-30 1:26 dpdklab
2023-09-30 1:26 dpdklab
2023-09-30 1:25 dpdklab
2023-09-30 1:25 dpdklab
2023-09-30 1:25 dpdklab
2023-09-30 1:25 dpdklab
2023-09-30 1:24 dpdklab
2023-09-30 1:24 dpdklab
2023-09-30 1:24 dpdklab
2023-09-30 1:24 dpdklab
2023-09-30 1:23 dpdklab
2023-09-30 1:23 dpdklab
2023-09-30 1:23 dpdklab
2023-09-30 1:22 dpdklab
2023-09-30 1:22 dpdklab
2023-09-30 1:22 dpdklab
2023-09-30 1:21 dpdklab
2023-09-30 1:21 dpdklab
2023-09-30 1:20 dpdklab
2023-09-30 1:20 dpdklab
2023-09-30 1:20 dpdklab
2023-09-30 1:19 dpdklab
2023-09-30 1:18 dpdklab
2023-09-30 1:18 dpdklab
2023-09-30 1:17 dpdklab
2023-09-30 1:17 dpdklab
2023-09-30 1:16 dpdklab
2023-09-30 1:16 dpdklab
2023-09-30 1:14 dpdklab
2023-09-30 1:14 dpdklab
2023-09-30 1:13 dpdklab
2023-09-30 1:13 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=651a203f.0c0a0220.475ce.4b46SMTPIN_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).