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] 850a57695b4647f62f31019baa8a92bcd3ff3531
Date: Fri, 23 Feb 2024 10:01:48 -0800 (PST) [thread overview]
Message-ID: <65d8dd8c.170a0220.b4b37.e3caSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-eventdev
850a57695b4647f62f31019baa8a92bcd3ff3531 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28109/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-23 18:01 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 18:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-24 2:51 dpdklab
2024-02-23 19:12 dpdklab
2024-02-23 18:48 dpdklab
2024-02-23 18:46 dpdklab
2024-02-23 18:39 dpdklab
2024-02-23 18:18 dpdklab
2024-02-23 18:08 dpdklab
2024-02-23 18:07 dpdklab
2024-02-23 18:06 dpdklab
2024-02-23 18:05 dpdklab
2024-02-23 18:04 dpdklab
2024-02-23 18:04 dpdklab
2024-02-23 18:02 dpdklab
2024-02-23 18:00 dpdklab
2024-02-23 18:00 dpdklab
2024-02-23 18:00 dpdklab
2024-02-23 17:58 dpdklab
2024-02-23 17:58 dpdklab
2024-02-23 17:58 dpdklab
2024-02-23 17:58 dpdklab
2024-02-23 17:56 dpdklab
2024-02-23 17:56 dpdklab
2024-02-23 17:55 dpdklab
2024-02-23 17:55 dpdklab
2024-02-23 17:55 dpdklab
2024-02-23 17:54 dpdklab
2024-02-23 17:53 dpdklab
2024-02-23 17:52 dpdklab
2024-02-23 17:51 dpdklab
2024-02-23 17:51 dpdklab
2024-02-23 17:51 dpdklab
2024-02-23 17:50 dpdklab
2024-02-23 17:50 dpdklab
2024-02-23 17:50 dpdklab
2024-02-23 17:49 dpdklab
2024-02-23 17:49 dpdklab
2024-02-23 17:49 dpdklab
2024-02-23 17:48 dpdklab
2024-02-23 17:48 dpdklab
2024-02-23 17:48 dpdklab
2024-02-23 17:48 dpdklab
2024-02-23 17:48 dpdklab
2024-02-23 17:47 dpdklab
2024-02-23 17:47 dpdklab
2024-02-23 17:47 dpdklab
2024-02-23 17:47 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=65d8dd8c.170a0220.b4b37.e3caSMTPIN_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).