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] 906d2c06b3cfc61620453c6909266fe771f8ccfb
Date: Mon, 29 Jan 2024 23:35:03 -0800 (PST) [thread overview]
Message-ID: <65b8a6a7.050a0220.7862d.48b4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
906d2c06b3cfc61620453c6909266fe771f8ccfb --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | SKIPPED | PASS |
+---------------------+--------------------+----------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27835/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-30 7:35 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 7:35 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 14:04 dpdklab
2024-01-30 13:42 dpdklab
2024-01-30 13:29 dpdklab
2024-01-30 13:26 dpdklab
2024-01-30 13:19 dpdklab
2024-01-30 12:57 dpdklab
2024-01-30 12:56 dpdklab
2024-01-30 12:50 dpdklab
2024-01-30 12:49 dpdklab
2024-01-30 12:26 dpdklab
2024-01-30 12:23 dpdklab
2024-01-30 12:23 dpdklab
2024-01-30 12:22 dpdklab
2024-01-30 12:18 dpdklab
2024-01-30 12:13 dpdklab
2024-01-30 11:07 dpdklab
2024-01-30 11:01 dpdklab
2024-01-30 10:47 dpdklab
2024-01-30 10:43 dpdklab
2024-01-30 10:41 dpdklab
2024-01-30 10:40 dpdklab
2024-01-30 10:37 dpdklab
2024-01-30 10:36 dpdklab
2024-01-30 10:33 dpdklab
2024-01-30 10:33 dpdklab
2024-01-30 10:32 dpdklab
2024-01-30 10:30 dpdklab
2024-01-30 10:28 dpdklab
2024-01-30 10:28 dpdklab
2024-01-30 10:27 dpdklab
2024-01-30 10:27 dpdklab
2024-01-30 10:25 dpdklab
2024-01-30 10:01 dpdklab
2024-01-30 9:18 dpdklab
2024-01-30 9:11 dpdklab
2024-01-30 9:11 dpdklab
2024-01-30 9:09 dpdklab
2024-01-30 9:08 dpdklab
2024-01-30 9:08 dpdklab
2024-01-30 9:07 dpdklab
2024-01-30 9:04 dpdklab
2024-01-30 9:04 dpdklab
2024-01-30 9:03 dpdklab
2024-01-30 8:19 dpdklab
2024-01-30 8:17 dpdklab
2024-01-30 8:05 dpdklab
2024-01-30 8:03 dpdklab
2024-01-30 7:57 dpdklab
2024-01-30 7:56 dpdklab
2024-01-30 7:56 dpdklab
2024-01-30 7:49 dpdklab
2024-01-30 7:43 dpdklab
2024-01-30 7:41 dpdklab
2024-01-30 7:39 dpdklab
2024-01-30 7:29 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=65b8a6a7.050a0220.7862d.48b4SMTPIN_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).