From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] a1934215a7691a86c55d415bd01ae8318581b67a
Date: Wed, 11 Oct 2023 18:50:57 -0700 (PDT) [thread overview]
Message-ID: <65275101.b00a0220.62412.10d2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
a1934215a7691a86c55d415bd01ae8318581b67a --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Arch Linux | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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/26439/
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-12 1:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 1:50 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-12 19:21 dpdklab
2023-10-12 12:22 dpdklab
2023-10-12 12:18 dpdklab
2023-10-12 12:17 dpdklab
2023-10-12 12:11 dpdklab
2023-10-12 3:24 dpdklab
2023-10-12 3:18 dpdklab
2023-10-12 3:17 dpdklab
2023-10-12 3:12 dpdklab
2023-10-12 3:12 dpdklab
2023-10-12 3:06 dpdklab
2023-10-12 2:44 dpdklab
2023-10-12 2:44 dpdklab
2023-10-12 2:40 dpdklab
2023-10-12 2:36 dpdklab
2023-10-12 2:35 dpdklab
2023-10-12 2:35 dpdklab
2023-10-12 2:34 dpdklab
2023-10-12 2:33 dpdklab
2023-10-12 2:33 dpdklab
2023-10-12 2:31 dpdklab
2023-10-12 2:30 dpdklab
2023-10-12 2:28 dpdklab
2023-10-12 2:02 dpdklab
2023-10-12 1:49 dpdklab
2023-10-12 1:48 dpdklab
2023-10-12 1:47 dpdklab
2023-10-12 1:37 dpdklab
2023-10-12 1:36 dpdklab
2023-10-12 1:36 dpdklab
2023-10-12 1:35 dpdklab
2023-10-12 1:35 dpdklab
2023-10-12 1:35 dpdklab
2023-10-12 1:34 dpdklab
2023-10-12 1:33 dpdklab
2023-10-12 1:33 dpdklab
2023-10-12 1:33 dpdklab
2023-10-12 1:32 dpdklab
2023-10-12 1:32 dpdklab
2023-10-12 1:32 dpdklab
2023-10-12 1:32 dpdklab
2023-10-12 1:31 dpdklab
2023-10-12 1:31 dpdklab
2023-10-12 1:30 dpdklab
2023-10-12 1:30 dpdklab
2023-10-12 1:29 dpdklab
2023-10-12 1:28 dpdklab
2023-10-12 1: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=65275101.b00a0220.62412.10d2SMTPIN_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).