From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 71f9da6691c49d0dfcf088dce5e99c488af0eb7e
Date: Wed, 01 Nov 2023 15:46:15 -0700 (PDT) [thread overview]
Message-ID: <6542d537.920a0220.d103a.7accSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
71f9da6691c49d0dfcf088dce5e99c488af0eb7e --> testing pass
Test environment and result as below:
+-----------------------+----------------+
| Environment | dpdk_unit_test |
+=======================+================+
| CentOS Stream 9 (ARM) | PASS |
+-----------------------+----------------+
| Fedora 37 (ARM) | PASS |
+-----------------------+----------------+
| Fedora 38 (ARM) | PASS |
+-----------------------+----------------+
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26769/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-01 22:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 22:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 11:05 dpdklab
2023-11-02 4:18 dpdklab
2023-11-02 1:13 dpdklab
2023-11-02 0:50 dpdklab
2023-11-01 23:30 dpdklab
2023-11-01 23:20 dpdklab
2023-11-01 23:13 dpdklab
2023-11-01 23:13 dpdklab
2023-11-01 23:13 dpdklab
2023-11-01 23:12 dpdklab
2023-11-01 23:11 dpdklab
2023-11-01 23:11 dpdklab
2023-11-01 23:10 dpdklab
2023-11-01 23:09 dpdklab
2023-11-01 22:57 dpdklab
2023-11-01 22:55 dpdklab
2023-11-01 22:54 dpdklab
2023-11-01 22:54 dpdklab
2023-11-01 22:45 dpdklab
2023-11-01 22:45 dpdklab
2023-11-01 22:44 dpdklab
2023-11-01 22:41 dpdklab
2023-11-01 22:29 dpdklab
2023-11-01 22:28 dpdklab
2023-11-01 22:28 dpdklab
2023-11-01 22:28 dpdklab
2023-11-01 22:27 dpdklab
2023-11-01 22:27 dpdklab
2023-11-01 22:27 dpdklab
2023-11-01 22:26 dpdklab
2023-11-01 22:25 dpdklab
2023-11-01 22:25 dpdklab
2023-11-01 22:24 dpdklab
2023-11-01 22:23 dpdklab
2023-11-01 22:23 dpdklab
2023-11-01 22:23 dpdklab
2023-11-01 21:19 dpdklab
2023-11-01 21:09 dpdklab
2023-11-01 21:09 dpdklab
2023-11-01 21:03 dpdklab
2023-11-01 20:27 dpdklab
2023-11-01 20:23 dpdklab
2023-11-01 20:19 dpdklab
2023-11-01 20:15 dpdklab
2023-11-01 20:15 dpdklab
2023-11-01 19:56 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=6542d537.920a0220.d103a.7accSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.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).