From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 0b82b5139fefe6eb5ec1a0b489fd193e8a99ab73
Date: Mon, 25 Mar 2024 17:29:56 -0700 (PDT) [thread overview]
Message-ID: <66021704.170a0220.b1ce0.9047SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
0b82b5139fefe6eb5ec1a0b489fd193e8a99ab73 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28627/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-26 0:29 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 0:29 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-01 19:10 dpdklab
2024-04-01 18:51 dpdklab
2024-04-01 18:47 dpdklab
2024-04-01 18:43 dpdklab
2024-04-01 18:39 dpdklab
2024-03-26 1:51 dpdklab
2024-03-26 1:26 dpdklab
2024-03-26 0:57 dpdklab
2024-03-26 0:51 dpdklab
2024-03-26 0:50 dpdklab
2024-03-26 0:48 dpdklab
2024-03-26 0:44 dpdklab
2024-03-26 0:43 dpdklab
2024-03-26 0:43 dpdklab
2024-03-26 0:42 dpdklab
2024-03-26 0:41 dpdklab
2024-03-26 0:41 dpdklab
2024-03-26 0:41 dpdklab
2024-03-26 0:39 dpdklab
2024-03-26 0:39 dpdklab
2024-03-26 0:39 dpdklab
2024-03-26 0:38 dpdklab
2024-03-26 0:37 dpdklab
2024-03-26 0:37 dpdklab
2024-03-26 0:36 dpdklab
2024-03-26 0:36 dpdklab
2024-03-26 0:36 dpdklab
2024-03-26 0:35 dpdklab
2024-03-26 0:33 dpdklab
2024-03-26 0:32 dpdklab
2024-03-26 0:32 dpdklab
2024-03-26 0:32 dpdklab
2024-03-26 0:32 dpdklab
2024-03-26 0:31 dpdklab
2024-03-26 0:31 dpdklab
2024-03-26 0:31 dpdklab
2024-03-26 0:30 dpdklab
2024-03-26 0:30 dpdklab
2024-03-26 0:29 dpdklab
2024-03-26 0:29 dpdklab
2024-03-26 0:28 dpdklab
2024-03-26 0:28 dpdklab
2024-03-26 0:28 dpdklab
2024-03-26 0:27 dpdklab
2024-03-26 0:27 dpdklab
2024-03-26 0:27 dpdklab
2024-03-26 0:27 dpdklab
2024-03-26 0:26 dpdklab
2024-03-26 0:26 dpdklab
2024-03-26 0:26 dpdklab
2024-03-26 0:26 dpdklab
2024-03-26 0:26 dpdklab
2024-03-26 0:25 dpdklab
2024-03-26 0:25 dpdklab
2024-03-26 0:25 dpdklab
2024-03-26 0:25 dpdklab
2024-03-26 0:25 dpdklab
2024-03-26 0:25 dpdklab
2024-03-26 0:24 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=66021704.170a0220.b1ce0.9047SMTPIN_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).