From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Qi Zhang <qi.z.zhang@intel.com>
Subject: |SUCCESS| [GIT MASTER] 74006a8024efa4cb590d9c6b2f1f99eb9a697a76
Date: Mon, 06 Nov 2023 16:34:03 -0800 (PST) [thread overview]
Message-ID: <654985fb.170a0220.bb5b8.a1e0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net-intel
74006a8024efa4cb590d9c6b2f1f99eb9a697a76 --> testing pass
Test environment and result as below:
+-----------------+--------------------+
| Environment | dpdk_meson_compile |
+=================+====================+
| Debian Bullseye | PASS |
+-----------------+--------------------+
| FreeBSD 13 | PASS |
+-----------------+--------------------+
| Fedora 38 | PASS |
+-----------------+--------------------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26852/
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-07 0:34 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 0:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-07 3:27 dpdklab
2023-11-07 1:07 dpdklab
2023-11-07 1:06 dpdklab
2023-11-07 1:03 dpdklab
2023-11-07 0:59 dpdklab
2023-11-07 0:55 dpdklab
2023-11-07 0:54 dpdklab
2023-11-07 0:53 dpdklab
2023-11-07 0:53 dpdklab
2023-11-07 0:53 dpdklab
2023-11-07 0:48 dpdklab
2023-11-07 0:47 dpdklab
2023-11-07 0:46 dpdklab
2023-11-07 0:45 dpdklab
2023-11-07 0:45 dpdklab
2023-11-07 0:45 dpdklab
2023-11-07 0:45 dpdklab
2023-11-07 0:45 dpdklab
2023-11-07 0:44 dpdklab
2023-11-07 0:44 dpdklab
2023-11-07 0:42 dpdklab
2023-11-07 0:41 dpdklab
2023-11-07 0:41 dpdklab
2023-11-07 0:40 dpdklab
2023-11-07 0:40 dpdklab
2023-11-07 0:40 dpdklab
2023-11-07 0:39 dpdklab
2023-11-07 0:39 dpdklab
2023-11-07 0:39 dpdklab
2023-11-07 0:39 dpdklab
2023-11-07 0:38 dpdklab
2023-11-07 0:38 dpdklab
2023-11-07 0:37 dpdklab
2023-11-07 0:37 dpdklab
2023-11-07 0:36 dpdklab
2023-11-07 0:36 dpdklab
2023-11-07 0:36 dpdklab
2023-11-07 0:35 dpdklab
2023-11-07 0:34 dpdklab
2023-11-07 0:34 dpdklab
2023-11-07 0:33 dpdklab
2023-11-07 0:33 dpdklab
2023-11-07 0:32 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=654985fb.170a0220.bb5b8.a1e0SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=qi.z.zhang@intel.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).